EP1343298B1 - Network-connecting apparatus and method for providing direct connections between network devices in different private networks - Google Patents

Network-connecting apparatus and method for providing direct connections between network devices in different private networks Download PDF

Info

Publication number
EP1343298B1
EP1343298B1 EP03004855A EP03004855A EP1343298B1 EP 1343298 B1 EP1343298 B1 EP 1343298B1 EP 03004855 A EP03004855 A EP 03004855A EP 03004855 A EP03004855 A EP 03004855A EP 1343298 B1 EP1343298 B1 EP 1343298B1
Authority
EP
European Patent Office
Prior art keywords
network
address
private
tunnel
public
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
Application number
EP03004855A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP1343298A2 (en
EP1343298A3 (en
Inventor
Won-Keun Kong
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.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co 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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of EP1343298A2 publication Critical patent/EP1343298A2/en
Publication of EP1343298A3 publication Critical patent/EP1343298A3/en
Application granted granted Critical
Publication of EP1343298B1 publication Critical patent/EP1343298B1/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/604—Address structures or formats
    • 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/2521—Translation architectures other than single NAT servers
    • H04L61/2535—Multiple local networks, e.g. resolving potential IP address conflicts

Definitions

  • This disclosure is related to a network-connecting apparatus and method. Specifically, techniques related to a network-connecting apparatus and method for providing direct connections between network devices in a first arbitrary private network and network devices in a second arbitrary private network are taught.
  • a device for IP communication over the Internet requires an IP address that is unique and distinguishable from another device.
  • the IP addresses that are presently allocated and used based on a code that is 32 bits long.
  • a scheme of using private IP addresses has been developed and employed to overcome this problem.
  • Private IP addresses are allocated on the condition that certain parts of the entire IP addresses can be used for tests or in local areas. Therefore these private addresses are freely usable for certain purposes.
  • regulations prohibit packets having a private IP address from being transferred to a public network.
  • An example of such a public network is the Internet.
  • An IP address that can be used in the public networks is called a public IP address.
  • Devices using a private IP address have various limitations.
  • the devices using public IP address have various other limitations, which could be different from the ones for devices with private IP addresses.
  • Private and public networks are connected to one another through a gateway.
  • Each gateway is dynamically allocated one public IP address. More public IP addresses are not allocated at least because that would increase the costs. That is, an Internet Service Provider (ISP) provides a public IP address for a gateway. This public IP address is required for connecting the gateway to the public network. Further, in a private network having a plurality of network devices, a public IP address is allocated to (and used for) the gateway only. For network devices other than the gateway, arbitrary private IP addresses are internally allocated. For ensuring complete communication access with other network devices it is desirable that a device that uses a private IP address performs at least the following different tasks.
  • ISP Internet Service Provider
  • NAT network address translation
  • NAPT network address port translation
  • This disclosure teaches a network-connecting apparatus for a first private network having a first network device.
  • the apparatus comprises a direct connection part for providing a direct connection in response to a connection request from the first network device, said request being a request to connect to a second network device in a second private network.
  • an address change part is provided for changing subnet numbers of origination and destination addresses of a packet transferred outside the first private network through the direct connection.
  • the direct connection part comprises an address acquisition part for acquiring a public IP address of the second private network from a domain name management server based on a domain name of the second network device received from the first network device, and for acquiring a private IP address of the second network device based on the received domain name.
  • a connection management part is provided for connecting to the second private network based on the acquired public IP address and forming a tunnel with the second private network.
  • an address mapping part is provided for converting the acquired public IP address and the acquired private IP address into an address system used in the first private network in case an address system used for the public IP address of the second private network is different from the address system used for the public IP address of the first private network.
  • the address change part comprises a number acquisition part for receiving a unique tunnel number from the second private network, said tunnel number being allocated to the tunnel.
  • a change part is provided for changing the subnet number of the origination address of the packet transferred outside the first private network through the direct connection to the tunnel number, and for changing the destination address of the packet to the acquired private IP address.
  • a registration request part for requesting a registration of a public IP address from a domain name management server, said public address being allocated from a unique domain name and internet service providing device through a communication network.
  • the direct connection part includes a connection management part for forming a tunnel with the second private network having the second network device.
  • the address change part comprises a number assignment part for assigning a unique tunnel number to the tunnel.
  • a change part is provided for changing a subnet number of the origination address of the packet transferred outside the first private network through the direct connection to the tunnel number, and for changing the destination address of the packet to a private IP address of the first network device.
  • the number assignment part assigns a number that is not a subnet number of the private IP address allocated to the second network device.
  • an authentication part for authenticating the second network device, wherein the direct connection part provides a direct connection in case of receiving a connection approval signal from the authentication part.
  • Another aspect of the disclosed teaching is a method for establishing connection between a first network device in a first private network and a second network device in a second private network.
  • the method comprises providing a direct connection in response to a connection request from the first network device to be connected to the second network device.
  • a private IP address of the second network device is acquired.
  • the subnet number of an origination address of a packet transferred outside the first private network through the direct connection is changed.
  • a destination address of the packet is changed to the private IP address of the second network device.
  • the direct connection includes acquiring a public IP address of the second private network from a domain name management server based on a domain name of the second network device received from the first network device. Connection is made to the second private network based on the acquired public IP address. A tunnel is formed with the second private network.
  • the direct connection further includes receiving a unique tunnel number allocated to the tunnel from the second private network.
  • the subnet number of the origination address of the packet is changed to the tunnel number.
  • the acquired public IP address and acquire private IP address are mapped into an address system used in the first private network address in case the address system used for the public address by the first private network is different from an address system used for the public IP address in the second private network.
  • a domain name management server prior to direct connection, is requested to register a public IP address allocated from a unique domain name and internet service providing device through a communication network.
  • the direct connection includes forming a tunnel with the second private network having the second network device.
  • a unique tunnel number is allocated to the tunnel.
  • Fig. 1 shows a structure of a network formed with network-connecting apparatuses according to an exemplary implementation of the disclosed teachings.
  • FIG. 1 an Internet Service Provider (ISP) 110, a Domain Name Server (DNS) 120, a Remote Server (RS) 130, a Remote Client (RC) 140, and plural gateways 152, 162, and 172, are connected to a public network 100.
  • This public network could be the Internet.
  • Gateway 152 acts as a passageway connecting the public network 100 and private network 150.
  • 162, and 172 act as passageways connecting private networks, 160, and 170, respectively, to the public network 100.
  • Private networks 150, 160, and 170 are connected to the gateways 152, 162, and 172 respectively. They are also connected to network devices 154a to 154n, 164a to 164n, and 174a to 174n, respectively.
  • the ISP 110 dynamically allocates public IP addresses in order to enable the respective gateways 152, 162, and 172 to connect to the Internet 100. Dynamic allocation in this context means that the same address need not be allocated to a gateway each time a new allocation is performed for the gateway.
  • the domain name server 120 links an internet address to a name.
  • the address is denoted by numbers, whereas the name is usually denoted by characters familiar to users. That is, the domain name server 120 stores and provides, to users, relations between continuously varying public IP addresses of the gateways 152, 162, and 172 and unique character names. Because of this, the users can easily recognize the public IP addresses of the gateways 152, 162, and 172 to which the users request a connection based on the names of corresponding gateways 152, 162, and 172.
  • the RS 130 is a general remote server providing services through the Internet 100.
  • the RC 140 is a general client devices using a public IP address.
  • the gateways 152, 162, and 172 are network-connecting apparatuses connecting the public network 100 and the private networks 150, 160, and 170. It should be noted that the gateways have both public IP addresses and private addresses.
  • the gateways 152, 162, and 172 employ a public IP address while connecting to the public network 100.
  • these gateways use private IP addresses while connecting to the private networks 150, 160, and 170.
  • the respective network devices 154a to 154n, 164a to 164n, and 174a to 174n form part of the private networks 150, 160, and 170, respectively. They use private IP addresses and they can be operated as servers or clients.
  • Fig. 2 is a block diagram showing an internal structure of a network-connecting apparatus according to an exemplary implementation of some aspects of the disclosed teachings.
  • the gateway 152 has a public network interface part 205, a private interface part 210, a routing part 215, a network address port translation (NAPT) part 220, a VPN part 225, a DNS part 230, an IP part 235, a direct connection part 240, an address change part 250, an address mapping part 260, a user authentication part 265, an encoding part 270, a first storage part 275, a second storage part 280, a third storage part 285, and a control part 290.
  • NAPT network address port translation
  • the public network interface part 205 is connected to the internet 100 through the ISP 110 and provides an interface with a broadband access network.
  • the broadband access could be provided through Asymmetric Digital Subscriber Line (ADSL), a Cable Modem, and the like.
  • the private network interface part 210 provides an interface with the private network 150 and employs an interface device with a LAN network having IP transfer capacity.
  • the private interface part 210 modifies the address part of the packet from or to the IP part 235 with the information from the direct connection part 240. However, in other cases, the packets from or to the IP part 235 are not modified.
  • the IP part 235 is in charge of receiving and transferring data between the network devices 154a to 154n in the private network 150 and the network devices 154a to 154n joined in the Virtual Private Network (VPN), also the IP part 235 is in charge of receiving and transferring data between the devices 154a to 154n in the private network 150 and the RC 140 in public network.
  • the routing part 215 performs a function of transferring data received or data to be transferred to the right destinations.
  • the NAPT part 220 is positioned between the public interface part 205 and the IP part 235 and translates private IP addresses into a public IP address in order to enable the plural network devices 154a to 154n that form part of the private network 150 to be connected to the Internet using only one shared public IP address.
  • the information required for the translation are stored and updated in a NAPT translation table that is stored in the first storage part 275.
  • the VPN part 225 forms a tunnel in order for the RS 130 and RC 140 connected to the Internet 100 to be connected to the private network 150. Likewise the VPN part 225 also forms a tunnel in order for the network devices 164a to 164n in a second private network 160 to be connected to the private network 150. In addition, the VPN part 225 allocates private IP addresses to the RS 130, the RC 140, and the network devices 164a to 164n in the second private network 160 which are connected through the tunnel. Further, the VPN part 225 also forms a tunnel for the gateway 160 of the second private network 160 in order for the network devices 154a to 154n that form part of the private network 150 to be connected to the second private network 160.
  • the DNS part 230 operates as a DNS server for the private network 150. Further, on initializing the system, the DNS part 230 requests a public IP address from the ISP 110. The DNS part 230 then registers the public IP address allocated from the ISP 110 and correlates it with a unique domain name of the private network 150. The public IP address and the name are registered with the domain name server 120 connected to the internet 100.
  • the direct connection part 240 provides direct connections between the network devices 154a to 154n inside the private network 150 and the network devices 164a to 164n that are outside the private network 150 and form part of a second private network 160.
  • the direct connection part 240 has an address acquisition part 242 and a connection management part 244.
  • the address acquisition part 242 acquires a public IP address from the Domain Name Server 120. For example, 208.229.23.30, is a public IP address of the private network 160 to be connected. This could be based on a domain name of the network device 164a, such as "lion.printer" that formed part of the network 160 that is waiting to be connected. This domain name is received from the network device 154a that forms part of the private network 150.
  • the connection management part 244 is connected to a gateway of the private network 160 (that is waiting to be connected), on a basis of the acquired IP address, to form a tunnel.
  • the address acquisition part 242 transfers the domain name of the network device 164a (the device whose connection is desired) to the gateway of the to-be-connected private network 160.
  • the address acquisition part 242 receives a private IP address of the corresponding network device 164a from the corresponding gateway 162.
  • the address acquisition part 242 changes a subnet number of the private IP address of the corresponding network device 164a to a tunnel number.
  • the address acquisition part 242 then transfers the tunnel number to the network device 154a requesting the connection.
  • connection-requesting network device 154a grasps that IP packets to be sent to the to-be-connected network device 164a and then transfer them to the gateway 162 of the private network 160 to which the network device 164a belongs.
  • the transfer is done using the process of Address Resolution Protocol (ARP) and is based on the changed private IP address of the to-be-connected network device 164a that is transferred to 154a.
  • ARP Address Resolution Protocol
  • physical network addresses should be obtained from the respective hosts and then matched with IP addresses.
  • the ARP is a protocol that performs a broadcast function in a network such as the Ethernet.
  • the private IP address of the to-be-connected network device 164a received from the gateway 162 of the private network to be connected is recorded in a translation table stored in the second storage part 275.
  • the private IP address of the connection-requesting network device 154a, and the tunnel number are also recorded in the translation table stored in the second storage part 275.
  • the connection-requesting network device 154a produces an IP packet designating a destination address. This designating address is formed by changing a subnet number of the private IP address of the to-be-connected network device 164a changed in a subnet number. It then makes a transfer request.
  • the address change part 250 changes a subnet number of an originating address of the produced IP packet to a tunnel number. It also changes the destination address of the produced IP packet to a private IP address of the to-be-connected network device 154a. In the meantime, the address change part 250 reads out the private IP address of the to-be-connected network device 164a, the private IP address of the connection-requesting network device 154a, and the tunnel number from the translation table stored in the second storage part 280 and performs an address change process.
  • the address change part 250 has a number acquisition part 252, a number assignment part 254, and a change part 256.
  • the number acquisition part 252 receives a unique tunnel number which is assigned to a tunnel formed from the gateway 162 of the to-be-connected private network 160.
  • the number assignment part 254 provided in the gateway 162 of the to-be-connected private network 160 assigns the tunnel number.
  • the gateway 162 of the to-be-connected private network 160 assigns a tunnel number
  • the gateway 162 considers a sub-netting method of the private network 160 corresponding to the gateway 162. That is, subnet numbers not assigned to the network devices 164a to 164n existing in the private network 160 corresponding to the gateway 162 are assigned as tunnel numbers. It is preferable that the number acquisition part 252 and the number assignment part 254 must cooperate to make the unique tunnel number.
  • the change part 256 changes the origination and destination addresses of an IP packet
  • gateway 162 may exchange sub-netting information with a connection-requesting gateway 152. This exchange of information is done such that the subnet numbers not used in both the gateways 152 and 162 can be used as tunnel numbers. In either case, it is desirable that the subnet numbers of private IP addresses used in the respective private networks 150 and 160 are fixed. This is done such that the subnet numbers not allocated in the respective private networks 150 and 160 can be allocated as tunnel numbers.
  • IP packet header Information on the origination and destination addresses is generally included in an IP packet header.
  • some network codes require that information about an address is included in a payload portion of an IP packet. Therefore, it is desirable that the gateway 152 has a packet identification part (not shown). This packet identification part can extract IP address information from an IP packet transferred from a private network in accordance with such network codes.
  • An IP packet in which an address change is completed is transferred to the gateway 162 of the to-be-connected private network 160 through a tunnel formed between the respective private networks 150 and 160.
  • the gateway 162 of the to-be-connected private network 160 transfers a received IP packet to the to-be-connected network device 164a.
  • an IP address system used in the private network 150 to which the connection-requesting network device 154a belongs is different from an IP address system used in the private network 160 to which the to-be-connected network device 164a belongs, for example IPv4.
  • the address mapping part 260 converts the address into a particular IP address system such as IPv6.
  • the conversion of an IP address system employs a method using a router and a domain name server which support both IPv4 and IPv6. It also employs a method for encapsulating an IPv6 diagram in an IPv4 packet, and so on. Detailed descriptions of these methods are omitted since they are well known to one skilled in the art.
  • a user authentication part 265 carries out an authentication process when connection requests originate from network devices 164a to 164n, RS 130, and RC 140, that do not form part of the private network 150.
  • User information necessary for user authentications is stored in the third storage part 285.
  • the direct connection part 240 forms a tunnel and provides a direct connection in case of receiving a connection approval signal for a network device such as the network device 164a requesting a connection from the user authentication part 265.
  • the encoding part 270 encodes data in case such additional security is required for packets communicating with devices connected to the Internet 100. Further, the encoding part 270 decodes the data received through the Internet 100. Information necessary to carry out the encoding and decoding of packets in the encoding part 270 is stored in the third storage part 285. The control part 290 controls the operations of the respective constituents of the overall system.
  • Fig. 3 shows an IP address structure and a subnet mask according to the IPv4 protocol.
  • an IP address is structured with a network address part 310 and a host address part 320.
  • a network is normally separated internally into several segments for better management.
  • the host address part 320 of the IP address 300 is divided into a subnet number part 330 and a host number part 340.
  • the subnet mask 350 is used to designate a broadcasting range.
  • the communication method of the Local Area Network (LAN) is the broadcasting method, separating one network class into plural network segments using subnet masking. This enables IP addresses to be efficiently used.
  • Fig. 3 shows a subnet mask 350 set to 255.255.255.0. Therefore, the subnet number part 330 of a 32-bit IP address 300 is included in a network number.
  • Fig. 4 shows a process of direct connections among network devices existing in different private networks by a network-connecting method according to an exemplary implementation of some aspects of the disclosed teachings.
  • a TV 405 that is part of a network A 410 having a domain name of tiger.tv requests a direct connection to a printer 465 existing in a network B 460 and having a domain name of lion.printer (S400). Both the TV 405 and the printer 465 have network functions.
  • the TV 405 transfers the domain name of the printer 465 to a gateway A and makes the request.
  • the gateway A 420 transfers the domain name of the printer 465 to a domain name server 440 holding public IP addresses of the network A 410 and network B 460. It then requests a public IP address of a private network to which the printer 465 belongs (S405).
  • the domain name server 440 provides the public IP address of the network B corresponding to the domain name of the printer 465 transferred from the gateway A 420 to the gateway A 420 (S410).
  • the gateway A 420 connects to the gateway B 450 and requests a tunnel formation (S415).
  • the gateway B 450 creates a tunnel having a unique tunnel number TN (S420). Prior to creating the tunnel, the gateway B 450 carries out a user authentication process and checks if TV 405 requesting the connection has the necessary connection authority. The tunnel is created only if such an authorization exists.
  • the gateway B 450 allocates the subnet numbers not assigned to network devices, existing in the network B 460, as tunnel numbers. If the respective networks 410 and 460 use the same sub-netting method, the subnet numbers not allocated in all of the respective networks 410 and 460 may be allocated as tunnel numbers.
  • the gateway B 450 When the gateway B 450 allocates a tunnel number, the gateway B 450 exchanges sub-netting information with the gateway A 420 and then allocates as a tunnel number a subnet number not used in all of the respective networks 410 and 460.
  • the subnet number parts of private IP addresses used in the respective networks 410 and 460 are preferably fixed so that a subnet number not assigned in the respective networks 410 and 460 can be allocated as a tunnel number.
  • the gateway A 420 requests a private IP address of the printer 465 to the gateway B 460 (S425).
  • the gateway B 460 in response to the request, provides a private IP address 172.16.0.9 of the printer 465 to the gateway B 420 (S430).
  • the gateway A 420 converts the provided subnet number of the private IP address of the printer 465 to a tunnel number and then transfers the tunnel number to the TV 405 (S435).
  • the TV 405 requests a transfer of IP packets in which its own private IP address and the converted private IP address of the printer 465 transferred from the gateway A 420 are recorded as the origination and destination addresses respectively (S440).
  • the origination and destination addresses of the IP packet transferred to the gateway A 420 from the TV 405 are 172.16.0.6 and 172.16.TN.9 respectively.
  • TN is the allocated tunnel number.
  • the gateway A 420 converts a subnet number of the origination address of the IP packet received from the TV 405 to a tunnel number, changes the destination address to a private IP address of the printer 465, and transfers the IP packet to the gateway B 450 (S445). Through such a conversion process, the origination and destination addresses of the IP packet transferred to the gateway B 450 from the gateway A 420 are converted into 172.16.TN.6 and 172.16.0.9 respectively.
  • the gateway B 460 transfers the received IP packet to the printer 465 (S450).
  • the respective gateways 420 and 460 carries out the steps S440 to S450 to provide direct communications between the TV 405 and the printer 465 (S455 to S465).
  • Fig. 5 shows an IP packet passing through a tunnel formed between the gateway A 420 and the gateway B 460.
  • the respective gateway 420 and 460 processes the exchange of an IP packet header tunnel number and a subnet number in the packet header of the TV/printer in a private network.
  • the network-connecting apparatus and method may be applied to a direct connection among network devices existing in a network having an address system according to the IPv6 and to a direct connection among network devices existing in a network having different address systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP03004855A 2002-03-07 2003-03-05 Network-connecting apparatus and method for providing direct connections between network devices in different private networks Expired - Fee Related EP1343298B1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2002-0012219A KR100485801B1 (ko) 2002-03-07 2002-03-07 서로 다른 사설망에 존재하는 네트워크장치들 간의직접접속을 제공하는 망접속장치 및 방법
KR2002012219 2002-03-07

Publications (3)

Publication Number Publication Date
EP1343298A2 EP1343298A2 (en) 2003-09-10
EP1343298A3 EP1343298A3 (en) 2004-06-30
EP1343298B1 true EP1343298B1 (en) 2005-06-22

Family

ID=27751993

Family Applications (1)

Application Number Title Priority Date Filing Date
EP03004855A Expired - Fee Related EP1343298B1 (en) 2002-03-07 2003-03-05 Network-connecting apparatus and method for providing direct connections between network devices in different private networks

Country Status (6)

Country Link
US (1) US7290060B2 (ko)
EP (1) EP1343298B1 (ko)
JP (1) JP3854584B2 (ko)
KR (1) KR100485801B1 (ko)
CN (1) CN100366033C (ko)
DE (1) DE60300871T2 (ko)

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69401040T2 (de) * 1993-07-12 1997-06-05 Nec Corp Gehäusestruktur für Mikrowellenschaltung
JP4010830B2 (ja) * 2002-03-05 2007-11-21 富士通株式会社 通信装置およびネットワークシステム
KR20030075810A (ko) * 2002-03-20 2003-09-26 유디에스 주식회사 공인네트워크와 비공인네트워크 사이에서의 데이터 통신시스템 및 그 방법
TW588532B (en) * 2002-03-29 2004-05-21 Realtek Semiconductor Corp Management device and method of NAT/NAPT session
TWI232655B (en) * 2002-05-07 2005-05-11 Realtek Semiconductor Corp Device and method for network address-port translation
KR100485769B1 (ko) * 2002-05-14 2005-04-28 삼성전자주식회사 서로 다른 홈네트워크에 존재하는 네트워크장치간의접속을 제공하기 위한 장치 및 방법
EP1429523A1 (en) * 2002-12-13 2004-06-16 Alcatel Public addressing supported by temporary private addressing
US20040153502A1 (en) * 2003-02-04 2004-08-05 Luliang Jiang Enhanced DNS server
US7944947B2 (en) * 2003-09-05 2011-05-17 Nokia Corporation Providing address information for reaching a wireless terminal
EP1667382A4 (en) * 2003-09-11 2006-10-04 Fujitsu Ltd PACKET RELAY DEVICE
GB2408415B (en) * 2003-11-19 2008-04-09 Vodafone Plc Networks
WO2005074208A1 (ja) * 2004-01-30 2005-08-11 Matsushita Electric Industrial Co., Ltd. 情報処理装置、サーバ、通信システム、アドレス決定方法、アドレス変更方法およびプログラム
US8065418B1 (en) * 2004-02-02 2011-11-22 Apple Inc. NAT traversal for media conferencing
JP4027347B2 (ja) * 2004-06-04 2007-12-26 キヤノン株式会社 情報処理装置、データ通信方法、プログラム及び記録媒体
US7912072B1 (en) * 2004-06-21 2011-03-22 Nortel Networks Limited Communication with a remote device
JP2006013827A (ja) * 2004-06-25 2006-01-12 Hitachi Communication Technologies Ltd パケット転送装置
JP4330520B2 (ja) * 2004-12-08 2009-09-16 富士通株式会社 通信装置
KR100785296B1 (ko) 2005-07-21 2007-12-12 삼성전자주식회사 Ｖｏｉｐ 게이트웨이에 있어서 데이터 전송 제어 장치 및그 방법
KR100736081B1 (ko) * 2005-11-11 2007-07-06 삼성전자주식회사 웹 서비스 제공 장치, 웹 서비스 요청 장치, 웹 서비스제공 방법 및 웹 서비스 요청 방법
US20070115898A1 (en) * 2005-11-22 2007-05-24 Stein Robert C Use of wireline networks to access 3G wireless services
US7609701B2 (en) 2006-02-22 2009-10-27 Zheng Yang Communication using private IP addresses of local networks
JP4238897B2 (ja) * 2006-08-24 2009-03-18 コニカミノルタビジネステクノロジーズ株式会社 ネットワークシステム、画像処理装置、及びプログラム
CN100502367C (zh) 2007-04-04 2009-06-17 华为技术有限公司 保存域名系统记录的方法、装置
CN101340331B (zh) * 2007-07-06 2010-12-08 中国电信股份有限公司 P2p网络中利用空闲终端执行系统任务的方法
US7926090B2 (en) * 2007-07-13 2011-04-12 Erf Wireless, Inc. Separate secure networks over a non-secure network
JP5335886B2 (ja) * 2008-03-20 2013-11-06 テレフオンアクチーボラゲット エル エム エリクソン（パブル） ローカル・ネットワーク間でデータ・パケットを通信するための方法および装置
US8856387B2 (en) * 2008-04-24 2014-10-07 Qualcomm Incorporated Local IP access scheme
US9658891B2 (en) * 2009-03-13 2017-05-23 Micro Focus Software Inc. System and method for providing key-encrypted storage in a cloud computing environment
KR100970367B1 (ko) * 2008-09-08 2010-07-15 주식회사 다산네트웍스 Ｉｐ 공유기의 동작 방법
CN101605154B (zh) * 2009-07-09 2014-08-13 中兴通讯股份有限公司 使用网络地址转换的网络设备的ip地址确认系统及方法
US8902743B2 (en) * 2010-06-28 2014-12-02 Microsoft Corporation Distributed and scalable network address translation
US8397958B2 (en) 2010-08-05 2013-03-19 Ds Smith Plastics Limited Closure valve assembly for a container
US20120311038A1 (en) 2011-06-06 2012-12-06 Trinh Trung Tim Proximity Session Mobility Extension
US10225354B2 (en) * 2011-06-06 2019-03-05 Mitel Networks Corporation Proximity session mobility
US9100399B2 (en) * 2012-06-29 2015-08-04 International Business Machines Corporation Portable virtual systems for composite solutions
CN103532935B (zh) * 2013-09-28 2017-01-18 福建星网锐捷软件有限公司 基于域策略的p2p流媒体传输控制方法
JP6056795B2 (ja) * 2014-03-25 2017-01-11 コニカミノルタ株式会社 画像処理システム、ゲートウェイ装置、ゲートウェイ装置の制御方法、ゲートウェイ装置の制御プログラム
JP6536050B2 (ja) * 2015-02-03 2019-07-03 コニカミノルタ株式会社 通信システム、制御装置、通信方法、およびコンピュータプログラム
JP6311666B2 (ja) * 2015-07-01 2018-04-18 コニカミノルタ株式会社 通信システム、管理サーバおよびプログラム
JP2021048526A (ja) * 2019-09-19 2021-03-25 富士ゼロックス株式会社 ネットワークシステム、ネットワークオペレーションセンタ、ネットワーク機器及びプログラム
US10992638B1 (en) * 2020-06-08 2021-04-27 Amazon Technologies, Inc. Network address translation based on logical channel implementation in a shared wireless network

Family Cites Families (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5777989A (en) * 1995-12-19 1998-07-07 International Business Machines Corporation TCP/IP host name resolution for machines on several domains
JP3436471B2 (ja) * 1997-05-26 2003-08-11 沖電気工業株式会社 電話通信方法及び電話通信システム
JPH11112577A (ja) 1997-10-08 1999-04-23 Hitachi Ltd Ｌａｎシステム間相互接続方式及びネットワークサービスシステム
US6079020A (en) * 1998-01-27 2000-06-20 Vpnet Technologies, Inc. Method and apparatus for managing a virtual private network
JP3581251B2 (ja) * 1998-06-16 2004-10-27 株式会社東芝 通信システム、データパケット転送方法、ルータ装置及びパケット中継装置
US6493349B1 (en) * 1998-11-13 2002-12-10 Nortel Networks Limited Extended internet protocol virtual private network architectures
JP2000228674A (ja) 1999-02-04 2000-08-15 Nippon Telegr & Teleph Corp <Ntt> 複数拠点間通信におけるアドレス割り当て方法及び複数拠点間の通信方法並びにその接続装置
US6393488B1 (en) * 1999-05-27 2002-05-21 3Com Corporation System and method for supporting internet protocol subnets with network address translators
US6801523B1 (en) * 1999-07-01 2004-10-05 Nortel Networks Limited Method and apparatus for performing internet protocol address resolutions in a telecommunications network
JP2001053778A (ja) * 1999-08-05 2001-02-23 Sony Corp 通信装置および方法、並びに媒体
US6523068B1 (en) * 1999-08-27 2003-02-18 3Com Corporation Method for encapsulating and transmitting a message includes private and forwarding network addresses with payload to an end of a tunneling association
US6781982B1 (en) * 1999-10-26 2004-08-24 3Com Corporation Method and system for allocating persistent private network addresses between private networks
US6708219B1 (en) * 1999-10-26 2004-03-16 3Com Corporation Method and system for dual-network address utilization
US6473863B1 (en) * 1999-10-28 2002-10-29 International Business Machines Corporation Automatic virtual private network internet snoop avoider
US6445922B1 (en) * 1999-12-15 2002-09-03 Lucent Technologies Inc. Method and system for support of overlapping IP addresses between an interworking function and a mobile IP foreign agent
KR100598336B1 (ko) * 1999-12-18 2006-07-06 주식회사 케이티 서비스 게이트웨이를 이용한 인터넷 ｖｐｎ서비스 제공방법
KR100604566B1 (ko) * 1999-12-22 2006-07-31 주식회사 케이티 세션 에이전트를 이용한 ｖｐｎ 서비스 제공방법
JP3478218B2 (ja) * 1999-12-27 2003-12-15 日本電気株式会社 エッジノード交換機と交換機
FR2806246B1 (fr) * 2000-03-08 2005-02-11 Sagem Procede d'appel, pour communiquer a travers un reseau informatique, d'un terminal d'un premier reseau cellulaire regional en deplacement dans la region d'un second reseau cellulaire regional
US6948003B1 (en) * 2000-03-15 2005-09-20 Ensim Corporation Enabling a service provider to provide intranet services
JP2001326693A (ja) * 2000-05-17 2001-11-22 Nec Corp 通信装置及び通信制御方法並びに制御プログラム記録媒体
KR100422375B1 (ko) * 2000-08-23 2004-03-16 큰사람컴퓨터 주식회사 상이한 아이피 어드레싱 체계를 갖는 네트워크 환경에접속된 터미널간의 연결을 설정하기 위한 방법 및 시스템
AU2001276948A1 (en) * 2000-08-24 2002-03-04 2Wire, Inc. System and method for selectively bridging and routing data packets between multiple networks
KR100645960B1 (ko) * 2000-08-29 2006-11-14 삼성전자주식회사 사설망의 네트워크 노드에 접속하기 위한 시스템과 방법
KR20020017265A (ko) * 2000-08-29 2002-03-07 구자홍 동일 아이피 서브넷상에 구성된 서로 다른 가상랜 사이의통신방법
US7092390B2 (en) * 2000-09-07 2006-08-15 Sbc Technology Resources, Inc. Internal substitution bi-level addressing for compatible public networks
US20020101859A1 (en) * 2000-09-12 2002-08-01 Maclean Ian B. Communicating between nodes in different wireless networks
US6778541B2 (en) * 2000-12-01 2004-08-17 Nortel Networks Limited Dynamic data tunnelling
US7155518B2 (en) * 2001-01-08 2006-12-26 Interactive People Unplugged Ab Extranet workgroup formation across multiple mobile virtual private networks
US20020103931A1 (en) * 2001-01-26 2002-08-01 Mott Charles J. Virtual private networking using domain name service proxy
TWI223942B (en) * 2001-02-20 2004-11-11 Li Jian Min Contents transmission network system and creating method thereof
US7072323B2 (en) * 2001-08-15 2006-07-04 Meshnetworks, Inc. System and method for performing soft handoff in a wireless data network
JP4186446B2 (ja) * 2001-09-11 2008-11-26 株式会社日立製作所 アドレス変換方法
US20030112808A1 (en) * 2001-12-13 2003-06-19 Net Reality Ltd Automatic configuration of IP tunnels
US20030154306A1 (en) * 2002-02-11 2003-08-14 Perry Stephen Hastings System and method to proxy inbound connections to privately addressed hosts
KR100485769B1 (ko) * 2002-05-14 2005-04-28 삼성전자주식회사 서로 다른 홈네트워크에 존재하는 네트워크장치간의접속을 제공하기 위한 장치 및 방법

Also Published As

Publication number Publication date
DE60300871T2 (de) 2005-11-24
JP2003273935A (ja) 2003-09-26
KR20030072927A (ko) 2003-09-19
EP1343298A2 (en) 2003-09-10
CN1444366A (zh) 2003-09-24
US20030172184A1 (en) 2003-09-11
US7290060B2 (en) 2007-10-30
EP1343298A3 (en) 2004-06-30
DE60300871D1 (de) 2005-07-28
KR100485801B1 (ko) 2005-04-28
JP3854584B2 (ja) 2006-12-06
CN100366033C (zh) 2008-01-30

Similar Documents

Publication Publication Date Title
EP1343298B1 (en) Network-connecting apparatus and method for providing direct connections between network devices in different private networks
US7796616B2 (en) Apparatus and method for offering connections between network devices located in different home networks
JP3735348B2 (ja) インターネットプロトコルアドレス変換装置、これを用いた通信ネットワークシステム及び通信方法
US7106739B2 (en) Method enabling network address translation of incoming session initiation protocol connections based on dynamic host configuration protocol address assignments
US7411967B2 (en) Private network gateways interconnecting private networks via an access network
US6490289B1 (en) Multiple network connections from a single PPP link with network address translation
EP2253123B1 (en) Method and apparatus for communication of data packets between local networks
US6580717B1 (en) Packet communication method and apparatus and a recording medium storing a packet communication program
US6381646B2 (en) Multiple network connections from a single PPP link with partial network address translation
JP3953955B2 (ja) アクセス・ネットワーク
US20030115345A1 (en) Methods and apparatus for masking destination addresses to reduce traffic over a communication link
JP2002502188A (ja) ネットワーク上のデスティネーションへ送信されたデータの経路決めをするドメイン名を使用するためのシステムおよび方法
WO2005027438A1 (ja) パケット中継装置
JP2004112801A (ja) Ｉｐアドレス割当装置及び方法
WO2012013133A1 (zh) 一种网络通信的方法和设备
US20060268863A1 (en) Transparent address translation methods
JP4571761B2 (ja) 仮想私設ネットワークにすでに接続されているユーザが、この仮想私設ネットワークに属さない通信デバイスと通信できるようにする方法および対応するネットワークアクセスサーバ
KR100587560B1 (ko) 링크 로컬 주소를 가지는 시스템에서 외부 시스템과통신하는 방법 및 장치
JPH11252172A (ja) パケット生成方法およびその機能を有する情報処理装置並びにパケット生成プログラムを記録した記録媒体
US20030142684A1 (en) LAN type internet access network and subscriber line accommodation method for use in the same network
US20030172142A1 (en) Method for building a vapa by using wireless-LAN interface card
KR20000046358A (ko) 라우터에서 인터넷 프로토콜 패킷의 원천지 주소 할당방법
KR20030058267A (ko) 중간 ｄｈｃｐ 서버를 이용한 중앙집중관리방식의 아이피자동할당 방법
JP2001136198A (ja) ネットワーク間通信方法およびサーバ装置並びにネットワーク間通信システム
Brustoloni et al. Application-independent end-to-end security in shared-link access networks

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20030305

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PT SE SI SK TR

AX Request for extension of the european patent

Extension state: AL LT LV MK RO

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

AKX Designation fees paid

Designated state(s): DE FR GB

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60300871

Country of ref document: DE

Date of ref document: 20050728

Kind code of ref document: P

ET Fr: translation filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20060323

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 14

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170221

Year of fee payment: 15

Ref country code: FR

Payment date: 20170223

Year of fee payment: 15

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20170222

Year of fee payment: 15

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60300871

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20180305

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181002

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180305

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180331