WO2005086427A1 - Tunneling service method and system - Google Patents

Tunneling service method and system Download PDF

Info

Publication number
WO2005086427A1
WO2005086427A1 PCT/KR2005/000309 KR2005000309W WO2005086427A1 WO 2005086427 A1 WO2005086427 A1 WO 2005086427A1 KR 2005000309 W KR2005000309 W KR 2005000309W WO 2005086427 A1 WO2005086427 A1 WO 2005086427A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
client node
packet
ipv4
message
Prior art date
Application number
PCT/KR2005/000309
Other languages
French (fr)
Inventor
Soo-Hong Park
Young-Keun Kim
Pyung-Soo Kim
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.
Priority to EP05726912A priority Critical patent/EP1712044A1/en
Priority to JP2006552044A priority patent/JP2007520970A/en
Publication of WO2005086427A1 publication Critical patent/WO2005086427A1/en

Links

Classifications

    • CCHEMISTRY; METALLURGY
    • C02TREATMENT OF WATER, WASTE WATER, SEWAGE, OR SLUDGE
    • C02FTREATMENT OF WATER, WASTE WATER, SEWAGE, OR SLUDGE
    • C02F1/00Treatment of water, waste water, or sewage
    • C02F1/72Treatment of water, waste water, or sewage by oxidation
    • C02F1/78Treatment of water, waste water, or sewage by oxidation with ozone
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4633Interconnection of networks using encapsulation techniques, e.g. tunneling
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B01PHYSICAL OR CHEMICAL PROCESSES OR APPARATUS IN GENERAL
    • B01FMIXING, e.g. DISSOLVING, EMULSIFYING OR DISPERSING
    • B01F23/00Mixing according to the phases to be mixed, e.g. dispersing or emulsifying
    • B01F23/20Mixing gases with liquids
    • B01F23/23Mixing gases with liquids by introducing gases into liquid media, e.g. for producing aerated liquids
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B01PHYSICAL OR CHEMICAL PROCESSES OR APPARATUS IN GENERAL
    • B01FMIXING, e.g. DISSOLVING, EMULSIFYING OR DISPERSING
    • B01F23/00Mixing according to the phases to be mixed, e.g. dispersing or emulsifying
    • B01F23/20Mixing gases with liquids
    • B01F23/23Mixing gases with liquids by introducing gases into liquid media, e.g. for producing aerated liquids
    • B01F23/237Mixing gases with liquids by introducing gases into liquid media, e.g. for producing aerated liquids characterised by the physical or chemical properties of gases or vapours introduced in the liquid media
    • B01F23/2376Mixing gases with liquids by introducing gases into liquid media, e.g. for producing aerated liquids characterised by the physical or chemical properties of gases or vapours introduced in the liquid media characterised by the gas being introduced
    • B01F23/23761Aerating, i.e. introducing oxygen containing gas in liquids
    • B01F23/237613Ozone
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B01PHYSICAL OR CHEMICAL PROCESSES OR APPARATUS IN GENERAL
    • B01FMIXING, e.g. DISSOLVING, EMULSIFYING OR DISPERSING
    • B01F25/00Flow mixers; Mixers for falling materials, e.g. solid particles
    • B01F25/30Injector mixers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present invention relates to a tunneling service enabling data communications between communication networks, and more particularly, to a tunneling service method and system enabling data communications between a client node having an IPv4/6 (Internet Protocol version 4/6) dual stack and a client node in a different network.
  • IPv4/6 Internet Protocol version 4/6
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • IPv4 is a network layer protocol operating according to a 32-bit IP (Internet Protocol) address.
  • IPv4 cannot satisfy the need for an increasing number of IP addresses for more Internet users.
  • IPv6 is based on a 128-bit address. IPv6, which allows for an extended header region in a packet, can define mechanisms guaranteeing packet source authentication, data perfection, and security.
  • IPv4-based and IPv6-based communication networks having different protocols IPv4 and IPv6 there has been a need for a tunneling service enabling data communication between a client node in the IPv4-based Internet communication network and a client node in the IPv6-based Internet communication network.
  • IPv4/6 dual stack client node has been suggested.
  • An IPv4 IP address and an IPv6 IP address of the IPv4/6 dual stack client node are provided by a DHCP (Dynamic Host Configuration Protocol) server or are input by the client.
  • the IPv4/6 dual stack client node can be connected to a client node linked to an IPv4-based Internet communication network and a client node in an IPv6-based Internet communication network using the IPv4 IP and IPv6 IP addresses.
  • an IPv6-over-IPv4 tunneling service is used. Disclosure of Invention Technical Problem
  • the IPv4/6 dual stack client node uses the address of a tunnel router or a tunnel end point input by the client.
  • the tunnel router and the tunnel end point are tunneling service servers. Therefore, the client of the IPv4/6 dual stack client node should be aware of the address of the tunnel router or the tunnel end point to be used. In addition, the client of the IPv4/6 dual stack node has to manually update the address of the tunnel router or the tunnel end point whenever the address of the tunnel router or the tunnel end point is altered.
  • a tunneling service method and system in which an address of a tunneling service server can be easily designated for a client node when a tunneling service enabling data communications between different communication networks is used.
  • a tunneling service method and system enabling data communications between different communication networks, in which an address of a tunneling service server can be easily designated for a client node by using dynamic host configuration protocol (DHCP) when an IPv6-over-IPv4 tunneling service is used.
  • DHCP dynamic host configuration protocol
  • a client can be automatically provided with the address of a tunneling service server, which may be a tunnel router or a tunnel end point, by the DHCPv4 server when using an IPv6-over-IPv4 tunneling service. Therefore, there is no need for the client to input the address of the tunneling service server when the address of the tunneling service server is altered, and IPv6-over-IPv4 tunneling can be achieved.
  • an IPv6-over-IPv4 tunneling service can be provided.
  • the client node can periodically provide the address of the tunneling service server. Description of Drawings
  • FIG. 1 illustrates a configuration of a tunneling service system according to an aspect of the present invention
  • FIG. 2 is a block diagram of an IPv4/6 client node in FIG. 1;
  • FIG. 3 illustrates a format of a dynamic host configuration protocol (DHCP) message
  • FIG. 4 is a table of the descriptions of fields in the DHCP message of FIG. 3;
  • FIG. 5 A illustrates a format of a DHCP message provided from a DHCPv4 server in FIG. 1;
  • FIG. 5B illustrates a format of a CTEP option field in FIG. 5A
  • FIG. 6 is a block diagram of the DHCPv4 server in FIG. 1;
  • FIG. 7 is a flowchart illustrating a tunneling service method according to an embodiment of the present invention. Best Mode
  • a tunneling service method for a client node in a network to which the client node, at least one DHCP server, and a tunnel router are connected including: transmitting an information request message, which requests information required for connection to the network, to a DHCP server selected by the client node; receiving an acknowledgement message, which contains an address of the tunnel router, from the DHCP server selected by the client node; and the client node detecting the address of the tunnel router contained in the acknowledgement message and generating a packet for a tunneling service using the detected address of the tunnel router.
  • the acknowledgement message may be a DHCP message, and the address of the tunnel router may be included in an option field of the DHCP message.
  • the generating of the packet may include: generating an IPv6 packet using the IPv6 IP address of the client node and an IPv6 IP address of a node for data communication with the client node; generating an IPv4 packet using the IPv4 IP address of the client node and the address of the tunnel router; and generating the packet for the tunneling service by encapsulating the IPv6 packet in the IPv4 packet.
  • a tunneling service method for a client node in a network to which the client node, a plurality of DHCP servers, and a plurality of tunnel routers are connected including: transmitting an information request message, which requests information required for connection to the network, to a DHCP server selected by the client node; receiving an acknowledgement message, which contains addresses of the plurality of tunnel routers, from the DHCP server selected by the client node; and the client node detecting and storing the addresses of the plurality of tunnel routers contained in the acknowledgement message, selecting the address of one of the tunnel routers, and generating a packet for a tunneling service using the address of the selected tunnel router.
  • a client node connected to a DHCP server and using a tunneling service, the client node including: a message transmitting and receiving unit transmitting and receiving a DHCP message with the DHCP server; a storing unit storing address information of the tunnel router; a control unit detecting the address of the tunnel router contained in a message received from the DHCP server via the message transmitting and receiving unit, storing the detected address of the tunnel router in the storing unit, and generating a packet for the tunneling service; and a packet generating unit generating the packet for the tunneling service under the control of the control unit.
  • control unit may select the address of one of the plurality of tunnel routers to generate the packet for the tunneling service.
  • the storing unit may store an IPv4 IP address and an IPv6 IP address of the client node in a dual stack.
  • a DHCP server supporting a tunneling service for a client node in a network
  • the server including: a storing unit storing address information of at least one tunnel router connected to the network; a message transmitting and receiving unit transmitting and receiving a DHCP message with the client node; and a control unit generating an option field containing the address information of the tunnel router stored in the storing unit when an information request message, which requests information required for connection to the network, is received from the message transmitting and receiving unit, and transmitting a DHCP message including the option field to the message transmitting and receiving unit.
  • control unit may update the address information of the tunnel router stored in the storing unit when the address information of the tunnel router is input by an operator of the DHCD server.
  • the control unit may incorporate temporal information for controlling the transmission period of the information request message from the client node into the dynamic host configuration protocol message including the option field.
  • a tunnelling service system provides an IPv6-over-IPv4 tunnelling service allowing data communication between an IPv4/6 client node 101 in an IPv4 network 100 and an IPv6 client node 111 in an IPv6 network 110.
  • the IPv4 network 100 is an IPv4-based Internet communication network
  • the IPv6 network 110 is an IPv6-based Internet communication network.
  • the IPv4 network 100 includes the IPv4/6 client node 101, a dynamic host configuration protocol (DHCPv4) server 102, a domain name server (DNS) 103, and a tunnel end point (TEP) 104.
  • the IPv4 network 100 may include a plurality of DHCPv4 servers.
  • the IPv6 network 110 includes an IPv6 client node 111.
  • the IPv4/6 client node 101 manages Internet Protocol (IP) addresses using a dual stack configuration.
  • IP Internet Protocol
  • An IP address of the IPv4/6 client node 101 in the IPv4 network 100 is provided by the DHCPv4 server 102 or is input by the client.
  • An IP address of the IPv4/6 client node 101 in the IPv6 network 110 is input by the client.
  • the IP addresses of the IPv4/6 client node 101 in the IPv4 network 100 and the IPv6 network 110 are stored in separate stacks. The IP addresses stored in the stacks are used as source addresses of the IPv4/6 client node 101 when the IPv4/6 client node 101 performs data communication with other client nodes.
  • the IPv4/6 client node 101 uses an IPv6-over-IPv4 tunneling service for data communication with the IPv6 client node 111.
  • the IPv4/6 client node 101 receives an IP address of the IPv6 client node 111, which is designated for data communication, from the DNS 103 and receives an IP address of the TEP 104, which is a tunnelling service server, from the DHCPv4 server 102.
  • the IPv4/6 client node 101 When the IP address of the TEP 104 is received from the DHCPv4 server 102, the IPv4/6 client node 101 generates a packet 105 for IPv6-over-IPv4 tunnelling and transmits the packet 105 to the TEP 104.
  • the IPv4/6 client node 101 includes a control unit 201, a DNS interface unit 202, a storing unit 203, and a message transmitting and receiving unit 204, and a packet generating unit 204, as shown in FIG. 2.
  • the control unit 201 receives an IP address of the IPv6 client node 111, which is designated for connection, from the DNS 103 via the DNS interface unit 202.
  • the received address of the IPv6 client node 111 is stored in the storing unit 203 under the control of the control unit 201.
  • the control unit 201 controls the message transmitting and receiving unit 204 to broadcast a DHCP message DHCPDISCOVER indicating that a DHCPv4 server is being searched for.
  • the DHCP message has a format illustrated in FIG. 3. Descriptions of fields of the DHCP message of FIG. 3 are in FIG. 4.
  • a relay agent appearing in FIG. 4 may exist between the IPv4/6 client node 101 and the DHCP4 server 102.
  • the control unit 201 selects a DHCPv4 server based on the received DHCPOFFER message.
  • the control unit 201 can select a DHCPv4 server based on the order in which the DHCPOFFER messages are received or DHCPv4 server information in an option field of each of the DHCPOFFER messages.
  • the DHCPv4 server information that can be included in the option field may be priority information of the DHCPv4 servers in the IPv4 network 100. If only one DHCPOFFER message is received, a DHCPv4 server that sent the received DHCPOFFER message is selected.
  • the control unit 201 broadcasts a DHCPREQUEST message, which is based on the information included in the DHCPOFFER message received from the selected DHCPv4 server, to the IPv4 network 100 via the message transmitting and receiving unit 204.
  • the DHCPREQUEST message is a message that requests network connection information, which is necessary for connection to the network.
  • the DHCPREQUEST message may include the IP address of the IPv4/6 client node 101, and the IP address and ID information of the DHCPv4 server that sent the DHCPOFFER message, which are included in the DHCPOFFER message. If the selected DHCPv4 server is the DHCPv4 server 102, the DHCPv4 server 102 receives the broadcasted DHCPREQUEST message.
  • the control unit 201 detects an IPv4 IP address included in the received DHCPACK message and stores it in an IP address stack for IPV4 (not shown).
  • the control unit 201 detects the address of the TEP 103 and stores it in the storing unit 203.
  • An IPv6 IP address of the IPv4/6 client node 101 is input by the client.
  • the control unit 201 stores the IPv6 IP address input by the client in an IP address stack for IPv6 (not shown).
  • the IP stack for IPv6 and the IP stack for IPv4 may be included in either the control unit 201 or the storing unit 203. If the IP stacks for IPv6 and IPv4 are included in the storing unit 203, the IPv4 IP address and IPv6 IP address of the IPv4/6 client node 101 are stored in the storing unit 203.
  • the control unit 201 stores such necessary network connection information in the storing unit 203.
  • the message transmitting and receiving unit 204 broadcasts the DHCP message to the IPV4 network 100 under the control of the control unit 201 and provides a received DHCP message to the control unit 201.
  • the message transmitting and receiving unit 204 transmits and receives a DHCP message with the selected DHCPv4 server under the control of the control unit 201.
  • the control unit 201 controls the packet generating unit 205 to generate an IPv6 packet including the IPv6 IP address in the stack as a source address and the previously received address of the IPv6 client node 111 as a destination address.
  • the control unit 201 controls the packet generating unit 204 to generate an IPv4 packet including the IPv4 IP address in the stack as a source address and the address of the TEP 104, which is stored in the storing unit 203, as a destination address.
  • the control unit 201 controls the packet generating unit 205 to transmit to the TEP 104 a packet in which the IPv6 packet is encapsulated in the IPV4 packet.
  • the control unit 201 selects one of the TEP addresses to generate the IPv4 packet.
  • the control unit 201 may select one of the TEP addresses according to a round-robin method. In this case, the traffic to the TEPs in the IPv4 network 100 can be distributed.
  • a plurality of TEP addresses may be received when the IPv4 network includes a plurality of TEPs.
  • the control unit 201 can transmit a DHCPREQUEST message to the DHCPv4 server 102 based on temporal information included in the received DHCPACK message.
  • the control unit 201 may monitor time and transmit the DHCPREQUEST message to the DHCPv4 server 102 within a time limit based on the temporal information.
  • the packet generating unit 205 generates the packet 105 as shown in FIG. 1 under the control of the control unit 201 for IPv6-over-IPv4 tunneling and transmits the generated packet to the IPv4 network 100.
  • the TEP 104 receives the packet 105.
  • the DHCPv4 server 102 in FIG. 1 provides the TEP address to the IPv4/6 client node 101 using the option field of the DHCP message of FIG. 3.
  • CTEP option field is one of optional parameters that can be defined in the option field in FIG. 3.
  • the CTEP option field in FIG. 5A includes an 8-bit option field type information (OPTION_CODE), an 8-bit information length information (LEN), and a plurality of 16-bit TEP addresses (CTEP ADDR 1 through CTEP ADDR n). Only one 16-bit TEP address may be included in the CTEP option field when the IPV4 network 100 includes one TEP 104.
  • OTION_CODE 8-bit option field type information
  • LEN 8-bit information length information
  • CTEP ADDR 1 through CTEP ADDR n 16-bit TEP addresses
  • FIG. 6 is a block diagram of the DHCPv4 server 102.
  • the DHCPv4 server 102 includes a control unit 601, a message transmitting and receiving unit 602, and a storing unit 603.
  • the control unit 601 controls the message transmitting and receiving unit 602 to broadcast a DHCPOFFER message.
  • the DHCPOFFER message includes the IP address and ID information of the DHCPv4 server 102 and the IPv4 IP address of the IPv4/6 client node 101 to the IPv4 network 100.
  • the control unit 601 After the DHCPOFFER message is transmitted and a DHCPREQUEST message, which requests necessary network connection information, is received from the IPv4/6 client node 101, the control unit 601 reads the network connection information including the address of the TEP 104 from the storing unit 603. The control unit 601 generates a CTEP option field based on the network connection information read from the storing unit 603, generates a DHCPACK message including the CTEP option field, and transmits the DHCPACK message to the IPV4/6 client node 101 via the message transmitting and receiving unit 602.
  • the TEP address stored in the storing unit 603 and the CTEP option field are updated.
  • the updated address of the TEP 104 or the address of the additional TEP may be input by an operator of the DCPv4 server 102.
  • the control unit 601 reads the TEP address from the storing unit 603 whenever a DHCPREQUEST message, which requires the CTEP option field, is received from the IPv4/6 client node 101, and transmits a DHCPACK message including the CTEP option field to the IPv4/6 client node 101.
  • the message transmitting and receiving unit 602 receives and transmits a DHCP message from the IPv4/6 client node 101 in the IPv4 network 100 under the control of the control unit 601.
  • the storing unit 603 stores addresses of TEPs in the IPv4 network 100.
  • the storing unit 603 can store any network connection information requested by the IPv4/6 client node 101.
  • IPv6 client nodes are registered with the DNS 103 in FIG. 1.
  • the DNS 103 provides an IPV6 IP address of the IPv6 client node 111 based on the domain name of the IPv6 client node 111 to the IPv4/6 client node 101.
  • the TEP 104 of FIG. 1 is a tunneling service server.
  • the TEP 104 can be also referred to as a tunnel router.
  • the TEP 104 decapsulates the IPv4 packet to detect the IPV6 packet and transmits the detected IPv6 packet to the IPv6 network 110.
  • the TEP 104 encapsulates the received IPv6 packet in the IPV4 packet received from the IPv4/6 client node 101 and transmits the encapsulated packet to the IPv4/6 client node 101.
  • the IPv6 client node 111 receives the IPv6 packet transmitted from the TEP 104 via the IPv6 network 110.
  • the IPv6 client node 111 receives the IPv6 packet using the destination address included in the IPv6 packet.
  • the IPv6 client node 111 processes data included in a payload area of the received IPv6 packet and transmits a cor- responding IPv6 packet to the IPv6 network 110.
  • a destination address included in the IPv6 packet transmitted from the IPv6 client node 111 is the IPv6 IP address of the IPv4/6 client node 101.
  • the IPv6 IP address of the IPv4/6 client node is managed in the TEP 104. Accordingly, the TEP 104 receives the IPv6 packet transmitted from the IPv6 client node 111.
  • the IPv6 client node 111 which functions according to IPv6, may be a mobile node, such as a notebook computer or a personal digital assistant (PDA), or a non- mobile node such as a desktop computer.
  • the IPv4/6 client node 101 which functions according to IPv4 and IPv6, may be a mobile node, such as a notebook computer or a PDA, or a non-mobile node, such as a desktop computer.
  • FIG. 7 is a flowchart of a tunneling service method according to an embodiment of the present invention.
  • the IPv4/6 client node 101 requests the DNS 103 for the IPv6 IP address of the IPv6 client node 111 (operation 701).
  • the IPv4/6 client node 101 broadcasts DHCPDISCOVER messages to the IPV4 network 100 (operation 703).
  • DHCPv4 servers in the IPv4 network 100 receive the DHCPDISCOVER messages, and the DHCPv4 servers broadcast a DHCPOFFER message (operation 704).
  • the IPv4/5 client node 101 selects a DHCPv4 server based on the information contained in the received DHCPOFFER message. If the IPv4/6 client node 101 selects the DHCPv4 server 102, the IPv4/6 client node 101 broadcasts a DHCPREQUEST message containing the IP address and ID information of the DHCPv4 server 102 and the IPv4 IP address of the IPv4/6 client node 101 to the IPv4 network 100 (operation 705).
  • the DHCPv4 server 102 receives the DHCPREQUEST message.
  • the DHCPv4 server 102 generates a CTEP option field as illustrated in FIG. 5B and generates a DHCP message including the CTEP option field (operation 706).
  • the CTEP option field includes at least one TEP address. Addresses of all TEPs in the IPv4 network 100 are included in the CTEP option field.
  • the DHCPv4 server 102 transmits the DHCPACK message including the CTEP option field to the IPv4/6 client node 101 (operation 707).
  • the IPv4/6 client node 101 detects and stores the TEP address CTEP ADDR included in the CTEP option field of the received DHCPACK message (operation 708). When there is a plurality of TEP addresses, the IPv4/6 client node 101 can select one TEP. The IPv4/6 client node 101 generates an IPv6 packet using the IPv6 IP address thereof previously stored in a stack and the IP address of the IPv6 client node 111 obtained in operation 702 (operation 709).
  • the IPv4/6 client node 101 generates an IPv4 packet using the IPv4 IP address thereof previously stored in a stack and the TEP address (operation 710).
  • the IPv4/6 client node 101 encapsulates the IPv6 packet in the IPv4 packet (operation 711).
  • the IPv4/6 client node 101 transmits the encapsulated packet to the TEP 104 via the IPv4 network 100 (operation 712).
  • the IPv4/6 client node 101 monitors time based on the temporal information included in the transmitted DHCPACK message (operation 713).
  • the IPv4/6 client node 101 transmits the DHCPREQUEST message to the DHCPv4 server 102 within a time limit defined in the temporal information to update the TEP address stored therein (operation 714).
  • the DHCPv4 server 102 transmits the DHCPACK message including the CTEP option field with the stored TEP address to the IPv4/6 client node 101. In this way, the IPv4/6 client node 101 can periodically receive TEP addresses from the DHCPv4 server 102. The IPv4/6 client node 101 returns to operation 708 and repeats the above- described operations.

Abstract

A tunneling service method and system enabling data communication between different networks, in which an address of a tunneling service server used in a client node can be easily designated, the tunneling service method includes: transmitting an information request message, which requests information required for connection to the network, to a dynamic host configuration protocol (DHCP) server selected by the client node; receiving an acknowledgement message, which contains an address of the tunnel router, from the DHCP server selected by the client node; and the client node detecting the address of the tunnel router contained in the acknowledgement message and generating a packet for a tunneling service using the detected address of the tunnel router.

Description

Description TUNNELING SERVICE METHOD AND SYSTEM Technical Field
[1] The present invention relates to a tunneling service enabling data communications between communication networks, and more particularly, to a tunneling service method and system enabling data communications between a client node having an IPv4/6 (Internet Protocol version 4/6) dual stack and a client node in a different network. Background Art
[2] Internet communication networks are categorized into IPv4 (Internet Protocol version 4)-based communication networks and IPv6 (Internet Protocol version 6)-based communication networks.
[3] IPv4 is a network layer protocol operating according to a 32-bit IP (Internet Protocol) address. However, IPv4 cannot satisfy the need for an increasing number of IP addresses for more Internet users.
[4] To solve the problem of insufficient Internet addresses, the Internet Engineering Task Force (IETF) has suggested the IPv6 as an Internet protocol next generation. IPv6 is based on a 128-bit address. IPv6, which allows for an extended header region in a packet, can define mechanisms guaranteeing packet source authentication, data perfection, and security.
[5] For IPv4-based and IPv6-based communication networks having different protocols IPv4 and IPv6, there has been a need for a tunneling service enabling data communication between a client node in the IPv4-based Internet communication network and a client node in the IPv6-based Internet communication network.
[6] An IPv4/6 dual stack client node has been suggested. An IPv4 IP address and an IPv6 IP address of the IPv4/6 dual stack client node are provided by a DHCP (Dynamic Host Configuration Protocol) server or are input by the client. The IPv4/6 dual stack client node can be connected to a client node linked to an IPv4-based Internet communication network and a client node in an IPv6-based Internet communication network using the IPv4 IP and IPv6 IP addresses. When the IPv4/6 dual stack client node is connected to an IPv6 client node in an IPv6-based Internet communication network, an IPv6-over-IPv4 tunneling service is used. Disclosure of Invention Technical Problem
[7] To use the IPv6-over-IPv4 tunneling service, the IPv4/6 dual stack client node uses the address of a tunnel router or a tunnel end point input by the client. The tunnel router and the tunnel end point are tunneling service servers. Therefore, the client of the IPv4/6 dual stack client node should be aware of the address of the tunnel router or the tunnel end point to be used. In addition, the client of the IPv4/6 dual stack node has to manually update the address of the tunnel router or the tunnel end point whenever the address of the tunnel router or the tunnel end point is altered. Technical Solution
[8] According to an aspect of the present invention, there is provided a tunneling service method and system in which an address of a tunneling service server can be easily designated for a client node when a tunneling service enabling data communications between different communication networks is used.
[9] According to an aspect of the present invention, there is provided a tunneling service method and system enabling data communications between different communication networks, in which an address of a tunneling service server can be easily designated for a client node by using dynamic host configuration protocol (DHCP) when an IPv6-over-IPv4 tunneling service is used. Advantageous Effects
[10] A client can be automatically provided with the address of a tunneling service server, which may be a tunnel router or a tunnel end point, by the DHCPv4 server when using an IPv6-over-IPv4 tunneling service. Therefore, there is no need for the client to input the address of the tunneling service server when the address of the tunneling service server is altered, and IPv6-over-IPv4 tunneling can be achieved. When a client is unaware of the address of the tunneling service server, an IPv6-over-IPv4 tunneling service can be provided.
[11] The client node can periodically provide the address of the tunneling service server. Description of Drawings
[12] FIG. 1 illustrates a configuration of a tunneling service system according to an aspect of the present invention;
[13] FIG. 2 is a block diagram of an IPv4/6 client node in FIG. 1;
[14] FIG. 3 illustrates a format of a dynamic host configuration protocol (DHCP) message;
[15] FIG. 4 is a table of the descriptions of fields in the DHCP message of FIG. 3;
[16] FIG. 5 A illustrates a format of a DHCP message provided from a DHCPv4 server in FIG. 1;
[17] FIG. 5B illustrates a format of a CTEP option field in FIG. 5A;
[18] FIG. 6 is a block diagram of the DHCPv4 server in FIG. 1; and
[19] FIG. 7 is a flowchart illustrating a tunneling service method according to an embodiment of the present invention. Best Mode
[20] According to an aspect of the present invention, there is provided a tunneling service method for a client node in a network to which the client node, at least one DHCP server, and a tunnel router are connected, the method including: transmitting an information request message, which requests information required for connection to the network, to a DHCP server selected by the client node; receiving an acknowledgement message, which contains an address of the tunnel router, from the DHCP server selected by the client node; and the client node detecting the address of the tunnel router contained in the acknowledgement message and generating a packet for a tunneling service using the detected address of the tunnel router.
[21] According to an aspect of the present invention, the acknowledgement message may be a DHCP message, and the address of the tunnel router may be included in an option field of the DHCP message.
[22] According to an aspect of the present invention, when the tunneling service method is applied to an IPv6-over-IPv4 tunneling service and the client node has an IPv4 IP address and an IPv6 IP address, the generating of the packet may include: generating an IPv6 packet using the IPv6 IP address of the client node and an IPv6 IP address of a node for data communication with the client node; generating an IPv4 packet using the IPv4 IP address of the client node and the address of the tunnel router; and generating the packet for the tunneling service by encapsulating the IPv6 packet in the IPv4 packet.
[23] According to an aspect of the present invention, there is also provided a tunneling service method for a client node in a network to which the client node, a plurality of DHCP servers, and a plurality of tunnel routers are connected, the method including: transmitting an information request message, which requests information required for connection to the network, to a DHCP server selected by the client node; receiving an acknowledgement message, which contains addresses of the plurality of tunnel routers, from the DHCP server selected by the client node; and the client node detecting and storing the addresses of the plurality of tunnel routers contained in the acknowledgement message, selecting the address of one of the tunnel routers, and generating a packet for a tunneling service using the address of the selected tunnel router.
[24] According to another aspect of the present invention, there is provided a client node connected to a DHCP server and using a tunneling service, the client node including: a message transmitting and receiving unit transmitting and receiving a DHCP message with the DHCP server; a storing unit storing address information of the tunnel router; a control unit detecting the address of the tunnel router contained in a message received from the DHCP server via the message transmitting and receiving unit, storing the detected address of the tunnel router in the storing unit, and generating a packet for the tunneling service; and a packet generating unit generating the packet for the tunneling service under the control of the control unit.
[25] According to an aspect of the invention, when there are a plurality of tunnel routers, the control unit may select the address of one of the plurality of tunnel routers to generate the packet for the tunneling service. When an IPv6-over-IPv4 tunneling service is used, the storing unit may store an IPv4 IP address and an IPv6 IP address of the client node in a dual stack.
[26] According to another aspect of the present invention, there is provided a DHCP server supporting a tunneling service for a client node in a network, the server including: a storing unit storing address information of at least one tunnel router connected to the network; a message transmitting and receiving unit transmitting and receiving a DHCP message with the client node; and a control unit generating an option field containing the address information of the tunnel router stored in the storing unit when an information request message, which requests information required for connection to the network, is received from the message transmitting and receiving unit, and transmitting a DHCP message including the option field to the message transmitting and receiving unit.
[27] According to an aspect of the invention, the control unit may update the address information of the tunnel router stored in the storing unit when the address information of the tunnel router is input by an operator of the DHCD server. The control unit may incorporate temporal information for controlling the transmission period of the information request message from the client node into the dynamic host configuration protocol message including the option field. Mode for Invention
[28] Reference will now be made in detail to the embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. The embodiments are described below to explain the present invention by referring to the figures.
[29] Referring to FIG. 1, a tunnelling service system according to an embodiment of the present invention provides an IPv6-over-IPv4 tunnelling service allowing data communication between an IPv4/6 client node 101 in an IPv4 network 100 and an IPv6 client node 111 in an IPv6 network 110. The IPv4 network 100 is an IPv4-based Internet communication network, and the IPv6 network 110 is an IPv6-based Internet communication network.
[30] As shown in FIG. 1, the IPv4 network 100 includes the IPv4/6 client node 101, a dynamic host configuration protocol (DHCPv4) server 102, a domain name server (DNS) 103, and a tunnel end point (TEP) 104. The IPv4 network 100 may include a plurality of DHCPv4 servers. The IPv6 network 110 includes an IPv6 client node 111.
[31] The IPv4/6 client node 101 manages Internet Protocol (IP) addresses using a dual stack configuration. An IP address of the IPv4/6 client node 101 in the IPv4 network 100 is provided by the DHCPv4 server 102 or is input by the client. An IP address of the IPv4/6 client node 101 in the IPv6 network 110 is input by the client. The IP addresses of the IPv4/6 client node 101 in the IPv4 network 100 and the IPv6 network 110 are stored in separate stacks. The IP addresses stored in the stacks are used as source addresses of the IPv4/6 client node 101 when the IPv4/6 client node 101 performs data communication with other client nodes.
[32] The IPv4/6 client node 101 uses an IPv6-over-IPv4 tunneling service for data communication with the IPv6 client node 111. To use a tunneling service, the IPv4/6 client node 101 receives an IP address of the IPv6 client node 111, which is designated for data communication, from the DNS 103 and receives an IP address of the TEP 104, which is a tunnelling service server, from the DHCPv4 server 102. When the IP address of the TEP 104 is received from the DHCPv4 server 102, the IPv4/6 client node 101 generates a packet 105 for IPv6-over-IPv4 tunnelling and transmits the packet 105 to the TEP 104.
[33] For the operation described above, the IPv4/6 client node 101 includes a control unit 201, a DNS interface unit 202, a storing unit 203, and a message transmitting and receiving unit 204, and a packet generating unit 204, as shown in FIG. 2.
[34] When an IPv6-over-IPv4 tunnelling service is used for a connection requested by a client, the control unit 201 receives an IP address of the IPv6 client node 111, which is designated for connection, from the DNS 103 via the DNS interface unit 202. The received address of the IPv6 client node 111 is stored in the storing unit 203 under the control of the control unit 201.
[35] The control unit 201 controls the message transmitting and receiving unit 204 to broadcast a DHCP message DHCPDISCOVER indicating that a DHCPv4 server is being searched for. The DHCP message has a format illustrated in FIG. 3. Descriptions of fields of the DHCP message of FIG. 3 are in FIG. 4. Although not illustrated in FIG. 1, a relay agent appearing in FIG. 4 may exist between the IPv4/6 client node 101 and the DHCP4 server 102.
[36] When the message transmitting and receiving unit 204 receives a DHCPOFFER message, the control unit 201 selects a DHCPv4 server based on the received DHCPOFFER message. The control unit 201 can select a DHCPv4 server based on the order in which the DHCPOFFER messages are received or DHCPv4 server information in an option field of each of the DHCPOFFER messages. The DHCPv4 server information that can be included in the option field may be priority information of the DHCPv4 servers in the IPv4 network 100. If only one DHCPOFFER message is received, a DHCPv4 server that sent the received DHCPOFFER message is selected.
[37] When a DHCPv4 server is selected, the control unit 201 broadcasts a DHCPREQUEST message, which is based on the information included in the DHCPOFFER message received from the selected DHCPv4 server, to the IPv4 network 100 via the message transmitting and receiving unit 204. The DHCPREQUEST message is a message that requests network connection information, which is necessary for connection to the network. The DHCPREQUEST message may include the IP address of the IPv4/6 client node 101, and the IP address and ID information of the DHCPv4 server that sent the DHCPOFFER message, which are included in the DHCPOFFER message. If the selected DHCPv4 server is the DHCPv4 server 102, the DHCPv4 server 102 receives the broadcasted DHCPREQUEST message.
[38] When the message transmitting and receiving unit 204 receives a DHCPACK message, which is an acknowledgement (ack) message acknowledging receipt of the DHCPREQUEST message, from the DHCPv4 server 102, the control unit 201 detects an IPv4 IP address included in the received DHCPACK message and stores it in an IP address stack for IPV4 (not shown). The control unit 201 detects the address of the TEP 103 and stores it in the storing unit 203. An IPv6 IP address of the IPv4/6 client node 101 is input by the client. The control unit 201 stores the IPv6 IP address input by the client in an IP address stack for IPv6 (not shown).
[39] The IP stack for IPv6 and the IP stack for IPv4 may be included in either the control unit 201 or the storing unit 203. If the IP stacks for IPv6 and IPv4 are included in the storing unit 203, the IPv4 IP address and IPv6 IP address of the IPv4/6 client node 101 are stored in the storing unit 203.
[40] When the DHCPACK message includes network connection information, which is necessary for connection to the network, such as mask information of the IPv4 network 100, default gateway information, etc., the control unit 201 stores such necessary network connection information in the storing unit 203.
[41] The message transmitting and receiving unit 204 broadcasts the DHCP message to the IPV4 network 100 under the control of the control unit 201 and provides a received DHCP message to the control unit 201. When one of DHCPv4 servers in the IPC4 network 100 is selected, the message transmitting and receiving unit 204 transmits and receives a DHCP message with the selected DHCPv4 server under the control of the control unit 201.
[42] The control unit 201 controls the packet generating unit 205 to generate an IPv6 packet including the IPv6 IP address in the stack as a source address and the previously received address of the IPv6 client node 111 as a destination address.
[43] The control unit 201 controls the packet generating unit 204 to generate an IPv4 packet including the IPv4 IP address in the stack as a source address and the address of the TEP 104, which is stored in the storing unit 203, as a destination address. The control unit 201 controls the packet generating unit 205 to transmit to the TEP 104 a packet in which the IPv6 packet is encapsulated in the IPV4 packet.
[44] When a plurality of TEP addresses are received from the DHCPv4 server 102, the control unit 201 selects one of the TEP addresses to generate the IPv4 packet. The control unit 201 may select one of the TEP addresses according to a round-robin method. In this case, the traffic to the TEPs in the IPv4 network 100 can be distributed. A plurality of TEP addresses may be received when the IPv4 network includes a plurality of TEPs.
[45] To update the TEP address, the control unit 201 can transmit a DHCPREQUEST message to the DHCPv4 server 102 based on temporal information included in the received DHCPACK message. In particular, the control unit 201 may monitor time and transmit the DHCPREQUEST message to the DHCPv4 server 102 within a time limit based on the temporal information.
[46] The packet generating unit 205 generates the packet 105 as shown in FIG. 1 under the control of the control unit 201 for IPv6-over-IPv4 tunneling and transmits the generated packet to the IPv4 network 100. The TEP 104 receives the packet 105.
[47] The DHCPv4 server 102 in FIG. 1 provides the TEP address to the IPv4/6 client node 101 using the option field of the DHCP message of FIG. 3. In particular, a DHCP message in which a conventional DHCP message field and a configured port tunnel end point (CTEP) option field, which is an additional field according to the present invention, are combined, as illustrated in FIG. 5A, is transmitted to IPv4/6 client node 101 as the DHCPACK message. The CTEP option field is one of optional parameters that can be defined in the option field in FIG. 3.
[48] As shown in FIG. 5B, the CTEP option field in FIG. 5A includes an 8-bit option field type information (OPTION_CODE), an 8-bit information length information (LEN), and a plurality of 16-bit TEP addresses (CTEP ADDR 1 through CTEP ADDR n). Only one 16-bit TEP address may be included in the CTEP option field when the IPV4 network 100 includes one TEP 104.
[49] FIG. 6 is a block diagram of the DHCPv4 server 102. Referring to FIG. 6, the DHCPv4 server 102 includes a control unit 601, a message transmitting and receiving unit 602, and a storing unit 603.
[50] When the message transmitting and receiving unit 602 receives the DHCPDISCOVER message broadcasted from the IPv4/6 client node 101, the control unit 601 controls the message transmitting and receiving unit 602 to broadcast a DHCPOFFER message. The DHCPOFFER message includes the IP address and ID information of the DHCPv4 server 102 and the IPv4 IP address of the IPv4/6 client node 101 to the IPv4 network 100.
[51 ] After the DHCPOFFER message is transmitted and a DHCPREQUEST message, which requests necessary network connection information, is received from the IPv4/6 client node 101, the control unit 601 reads the network connection information including the address of the TEP 104 from the storing unit 603. The control unit 601 generates a CTEP option field based on the network connection information read from the storing unit 603, generates a DHCPACK message including the CTEP option field, and transmits the DHCPACK message to the IPV4/6 client node 101 via the message transmitting and receiving unit 602.
[52] When the address of the TEP 104 in the IPv4 network 100 is altered or when another TEP is added into the IPv4 network 100, the TEP address stored in the storing unit 603 and the CTEP option field are updated. The updated address of the TEP 104 or the address of the additional TEP may be input by an operator of the DCPv4 server 102.
[53] The control unit 601 reads the TEP address from the storing unit 603 whenever a DHCPREQUEST message, which requires the CTEP option field, is received from the IPv4/6 client node 101, and transmits a DHCPACK message including the CTEP option field to the IPv4/6 client node 101.
[54] The message transmitting and receiving unit 602 receives and transmits a DHCP message from the IPv4/6 client node 101 in the IPv4 network 100 under the control of the control unit 601. The storing unit 603 stores addresses of TEPs in the IPv4 network 100. The storing unit 603 can store any network connection information requested by the IPv4/6 client node 101.
[55] Domain names and addresses of IPv6 client nodes are registered with the DNS 103 in FIG. 1. When the IPv4/6 client node 101 requests an address of the IPv6 client node 111, the DNS 103 provides an IPV6 IP address of the IPv6 client node 111 based on the domain name of the IPv6 client node 111 to the IPv4/6 client node 101.
[56] The TEP 104 of FIG. 1 is a tunneling service server. The TEP 104 can be also referred to as a tunnel router. When the packet 105 is received from the IPv4/6 client node 101, the TEP 104 decapsulates the IPv4 packet to detect the IPV6 packet and transmits the detected IPv6 packet to the IPv6 network 110. When the IPv6 packet is received from the IPv6 network 110, the TEP 104 encapsulates the received IPv6 packet in the IPV4 packet received from the IPv4/6 client node 101 and transmits the encapsulated packet to the IPv4/6 client node 101.
[57] The IPv6 client node 111 receives the IPv6 packet transmitted from the TEP 104 via the IPv6 network 110. The IPv6 client node 111 receives the IPv6 packet using the destination address included in the IPv6 packet. The IPv6 client node 111 processes data included in a payload area of the received IPv6 packet and transmits a cor- responding IPv6 packet to the IPv6 network 110. A destination address included in the IPv6 packet transmitted from the IPv6 client node 111 is the IPv6 IP address of the IPv4/6 client node 101. The IPv6 IP address of the IPv4/6 client node is managed in the TEP 104. Accordingly, the TEP 104 receives the IPv6 packet transmitted from the IPv6 client node 111.
[58] The IPv6 client node 111, which functions according to IPv6, may be a mobile node, such as a notebook computer or a personal digital assistant (PDA), or a non- mobile node such as a desktop computer. The IPv4/6 client node 101, which functions according to IPv4 and IPv6, may be a mobile node, such as a notebook computer or a PDA, or a non-mobile node, such as a desktop computer.
[59] FIG. 7 is a flowchart of a tunneling service method according to an embodiment of the present invention.
[60] When the client inputs a domain name of the IPv6 client node 111, the IPv4/6 client node 101 requests the DNS 103 for the IPv6 IP address of the IPv6 client node 111 (operation 701). When the IPv6 IP address of the IPv6 client node 111 is received from the DNS 103 (operation 701), the IPv4/6 client node 101 broadcasts DHCPDISCOVER messages to the IPV4 network 100 (operation 703).
[61] DHCPv4 servers in the IPv4 network 100 receive the DHCPDISCOVER messages, and the DHCPv4 servers broadcast a DHCPOFFER message (operation 704). The IPv4/5 client node 101 selects a DHCPv4 server based on the information contained in the received DHCPOFFER message. If the IPv4/6 client node 101 selects the DHCPv4 server 102, the IPv4/6 client node 101 broadcasts a DHCPREQUEST message containing the IP address and ID information of the DHCPv4 server 102 and the IPv4 IP address of the IPv4/6 client node 101 to the IPv4 network 100 (operation 705). The DHCPv4 server 102 receives the DHCPREQUEST message.
[62] The DHCPv4 server 102 generates a CTEP option field as illustrated in FIG. 5B and generates a DHCP message including the CTEP option field (operation 706). The CTEP option field includes at least one TEP address. Addresses of all TEPs in the IPv4 network 100 are included in the CTEP option field. The DHCPv4 server 102 transmits the DHCPACK message including the CTEP option field to the IPv4/6 client node 101 (operation 707).
[63] The IPv4/6 client node 101 detects and stores the TEP address CTEP ADDR included in the CTEP option field of the received DHCPACK message (operation 708). When there is a plurality of TEP addresses, the IPv4/6 client node 101 can select one TEP. The IPv4/6 client node 101 generates an IPv6 packet using the IPv6 IP address thereof previously stored in a stack and the IP address of the IPv6 client node 111 obtained in operation 702 (operation 709).
[64] The IPv4/6 client node 101 generates an IPv4 packet using the IPv4 IP address thereof previously stored in a stack and the TEP address (operation 710).
[65] The IPv4/6 client node 101 encapsulates the IPv6 packet in the IPv4 packet (operation 711). The IPv4/6 client node 101 transmits the encapsulated packet to the TEP 104 via the IPv4 network 100 (operation 712).
[66] The IPv4/6 client node 101 monitors time based on the temporal information included in the transmitted DHCPACK message (operation 713). The IPv4/6 client node 101 transmits the DHCPREQUEST message to the DHCPv4 server 102 within a time limit defined in the temporal information to update the TEP address stored therein (operation 714).
[67] The DHCPv4 server 102 transmits the DHCPACK message including the CTEP option field with the stored TEP address to the IPv4/6 client node 101. In this way, the IPv4/6 client node 101 can periodically receive TEP addresses from the DHCPv4 server 102. The IPv4/6 client node 101 returns to operation 708 and repeats the above- described operations.
[68] While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the following claims.

Claims

Claims
[1] 1. A tunneling service method of a client node in a network to which the client node, at least one dynamic host configuration protocol (DHCP) server, and a tunnel router are connected, the method comprising: transmitting an information request message, which requests information required for connection to the network, to the at least one DHCP server selected by the client node; receiving an acknowledgement message, which contains an address of the tunnel router, from the DHCP server selected by the client node; and the client node detecting the address of the tunnel router contained in the acknowledgement message and generating a packet for a tunneling service using the detected address of the tunnel router.
[2] 2. The tunneling service method of claim 1, wherein the acknowledgement message is a dynamic host configuration protocol (DHCP) message, and the address of the tunnel router is included in an option field of the DHCP message.
[3] 3. The tunneling service method of claim 1, wherein the information request message is periodically transmitted based on temporal information included in the acknowledgement message.
[4] 4. The tunneling service method of claim 1, which when applied to an IPv6-over-IPv4 tunneling service and the client node having an IPv4 IP address and an IPv6 IP address, the generating of the packet comprises: generating an IPv6 packet using the IPv6 IP address of the client node and another IPv6 IP address of a node for data communication with the client node; generating an IPv4 packet using the IPv4 IP address of the client node and the address of the tunnel router; and generating the packet for the tunneling service by encapsulating the IPv6 packet in the IPv4 packet.
[5] 5. A tunneling service method of a client node in a network to which the client node, a plurality of dynamic host configuration protocol (DHCP) servers, and a plurality of tunnel routers are connected, the method comprising: transmitting an information request message, which requests information required for connection to the network, to at least one DHCP server selected by the client node; receiving an acknowledgement message, which contains addresses of the plurality of tunnel routers, from the at least one DHCP server selected by the client node; and the client node detecting and storing the addresses of the plurality of tunnel routers contained in the acknowledgement message, selecting an address of one of the tunnel routers, and generating a packet for a tunneling service using the address of the selected tunnel router.
[6] 6. The tunneling service method of claim 5, wherein the packet is generated by encapsulating an IPv6 packet in an IPv4 packet.
[7] 7. The tunneling service method of claim 5, wherein the client node is automatically provided with the addresses of the plurality of tunnel routers.
[8] 8. A client node connected to a dynamic host configuration protocol (DHCP) server and using a tunneling service, the client node comprising: a message transmitting and receiving unit transmitting and receiving a DHCP message from the DHCP server; a storing unit storing address information of a tunnel router; a control unit detecting an address of the tunnel router contained in a message received from the DHCP server via the message transmitting and receiving unit, storing the detected address of the tunnel router in the storing unit, and generating a packet for the tunneling service; and a packet generating unit generating the packet for the tunneling service under control of the control unit.
[9] 9. The client node of claim 8, wherein, when there are a plurality of tunnel routers, the control unit selects an address of one of the plurality of tunnel routers to generate the packet for the tunneling service.
[10] 10. The client node of claim 8, wherein, when an IPv6-over-IPv4 tunneling service is used, the storing unit stores an IPv4 IP address and an IPv6 IP address of the client node in a dual stack.
[11] 11. The client node of claim 10, wherein the control unit generates an IPv6 packet using the IPv6 IP address of the client node and another IPv6 IP address of a node for data communication with the client node, generates an IPv4 packet using the IPv4 IP address of the client node and the address of the tunnel router, and generating the packet for the tunneling service by encapsulating the IPv6 packet in the IPv4 packet.
[12] 12. The client node of claim 8, wherein the client node includes a mobile node, or a non-mobile node.
[13] 13. A dynamic host configuration protocol (DHCP) server supporting a tunneling service for a client node in a network, the DHCP server comprising: a storing unit storing address information of at least one tunnel router connected to the network; a message transmitting and receiving unit transmitting and receiving a DHCP message with the client node; and a control unit generating an option field containing the address information of the at least one tunnel router stored in the storing unit when an information request message, which requests information required for connection to the network, is received from the message transmitting and receiving unit, and transmitting the DHCP message including the option field to the message transmitting and receiving unit.
[14] 14. The dynamic host configuration protocol server of claim 13, wherein the control unit updates the address information of the at least one tunnel router stored in the storing unit when the address information of the at least one tunnel router is input by an operator of the DHCD server.
[15] 15. The dynamic host configuration protocol of claim 13, wherein the control unit incorporates temporal information for controlling a transmission period of the information request message from the client node into the DHCP message including the option filed.
[16] 16. A tunneling service method of a client node in a network, the method comprising: transmitting an information request message requesting information for connecting to the network; receiving an acknowledgement message containing an address of a tunnel router for connecting to the network; and detecting the address of the tunnel router contained in the acknowledgement message and generating a packet for a tunneling service using the detected address of the tunnel router.
[17] 17. The tunneling service method of claim 16, wherein the acknowledgment message is a dynamic host configuration protocol (DHCP) message, and the address of the tunnel router is included in the DHCP message.
[18] 18. The tunneling service method of claim 16, wherein the packet is generated by encapsulating an IPv6 packet in an IPv4 packet.
[19] 19. The tunneling service method of claim 16, wherein the client node is automatically provided with the addresses of the plurality of tunnel routers.
[20] 20. The tunneling service method of claim 18, wherein the IPv4 packet is generated using an IPv4 IP address of the client node and the address of the tunnel router, and the IPv6 packet is generated using an IPv6 IP address of the client node and another IPv6 IP address of another node for data communication with the client node.
PCT/KR2005/000309 2004-02-05 2005-02-02 Tunneling service method and system WO2005086427A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP05726912A EP1712044A1 (en) 2004-02-05 2005-02-02 Tunneling service method and system
JP2006552044A JP2007520970A (en) 2004-02-05 2005-02-02 Tunneling service method and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2004-0007669 2004-02-05
KR1020040007669A KR20050079420A (en) 2004-02-05 2004-02-05 Tunnelling sevice method and system thereof

Publications (1)

Publication Number Publication Date
WO2005086427A1 true WO2005086427A1 (en) 2005-09-15

Family

ID=36968338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2005/000309 WO2005086427A1 (en) 2004-02-05 2005-02-02 Tunneling service method and system

Country Status (7)

Country Link
US (2) US20050175020A1 (en)
EP (1) EP1712044A1 (en)
JP (1) JP2007520970A (en)
KR (1) KR20050079420A (en)
CN (2) CN101321111A (en)
TW (1) TWI294732B (en)
WO (1) WO2005086427A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761553B2 (en) 2005-11-29 2010-07-20 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in an access system
US9386047B2 (en) 2012-03-14 2016-07-05 Huawei Technologies Co., Ltd. Method, switch, server and system for sending connection establishment request

Families Citing this family (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1266507B1 (en) * 2000-03-17 2004-06-02 America Online, Inc. Home-networking
US7051116B1 (en) * 2001-06-21 2006-05-23 America Online, Inc. Client device identification when communicating through a network address translator device
US7383339B1 (en) 2002-07-31 2008-06-03 Aol Llc, A Delaware Limited Liability Company Local proxy server for establishing device controls
US7337219B1 (en) 2003-05-30 2008-02-26 Aol Llc, A Delaware Limited Liability Company Classifying devices using a local proxy server
US7437457B1 (en) 2003-09-08 2008-10-14 Aol Llc, A Delaware Limited Liability Company Regulating concurrent logins associated with a single account
KR20060009676A (en) * 2004-07-26 2006-02-01 삼성전자주식회사 Method and apparatus for configuring a tunnel automatically
JP3996922B2 (en) * 2004-11-05 2007-10-24 株式会社インターネットイニシアティブ Centralized management system and method for network connection means in a network where different communication protocols coexist
US20060203774A1 (en) * 2005-03-10 2006-09-14 Nokia Corporation System, method and apparatus for selecting a remote tunnel endpoint for accessing packet data services
JP4421517B2 (en) * 2005-06-07 2010-02-24 株式会社東芝 Information processing server, remote operation system, and remote operation method
US7613131B2 (en) * 2005-11-10 2009-11-03 Citrix Systems, Inc. Overlay network infrastructure
US7860088B2 (en) * 2005-12-01 2010-12-28 Qualcomm Incorporated Concurrent internet protocol connectivity to an access terminal and a tethered device
JP4639152B2 (en) * 2006-01-20 2011-02-23 株式会社日立製作所 Communications system
JP4585479B2 (en) * 2006-03-30 2010-11-24 株式会社東芝 Server apparatus and video distribution method
FR2903263A1 (en) * 2006-06-30 2008-01-04 France Telecom METHOD FOR ADDRESSING SERVICE ELEMENTS AND CALL TRANSMISSION BETWEEN HETEROGENEOUS NODES
CN101102308B (en) * 2006-07-04 2010-12-22 宽宇科技有限公司 Internet protocol channel management method
KR100745724B1 (en) * 2006-09-29 2007-08-03 한국전자통신연구원 Method for the service perception of router in ipv6
KR100901790B1 (en) 2006-12-04 2009-06-11 한국전자통신연구원 CONTROL TUNNEL AND DIRECT TUNNEL CONFIGURATION METHOD IN IPv6 SERVICE PROVIDE SYSTEM BASED IPv4 NETWORK
US20080259941A1 (en) * 2007-04-19 2008-10-23 At&T Knowledge Ventures, L.P. System and apparatus for managing ip addresses
US20090290539A1 (en) * 2008-05-21 2009-11-26 Huawei Technologies, Co., Ltd. Method and apparatus for home agent address acquisition for IPv4 mobile nodes
CN101674221A (en) * 2008-09-09 2010-03-17 中国移动通信集团公司 Static routing generation method, method and device for implementing terminal routing
CN101854285A (en) * 2009-04-03 2010-10-06 华为技术有限公司 Carrier-grade network address translation equipment discovery method, equipment and system
CN101938526A (en) * 2009-06-30 2011-01-05 中兴通讯股份有限公司 Obtaining method of routing policy, terminal and server
CN102158563B (en) * 2010-02-12 2013-10-30 华为技术有限公司 Method, system and device for acquiring IPv6 (Internet Protocol Version 6) configuration information from IPv6 transition network
KR20110119526A (en) * 2010-04-26 2011-11-02 삼성전자주식회사 Method and apparatus for transmitting ethernet data through audio/video interface
CN102271050B (en) * 2010-06-04 2014-04-30 华为技术有限公司 Method and system for automatically configuring network equipment in Internet protocol version 6 (IPv6) network, and network equipment
CN102710803B (en) * 2012-05-08 2016-03-30 中兴通讯股份有限公司 The method and system of IPv6 DNS information are issued in IPv4 network
US20140256286A1 (en) * 2013-03-08 2014-09-11 Microsoft Corporation Intelligent Protocol Selection
US9769078B2 (en) 2013-11-05 2017-09-19 Cisco Technology, Inc. Dynamic flowlet prioritization
US9825857B2 (en) 2013-11-05 2017-11-21 Cisco Technology, Inc. Method for increasing Layer-3 longest prefix match scale
US9655232B2 (en) 2013-11-05 2017-05-16 Cisco Technology, Inc. Spanning tree protocol (STP) optimization techniques
US9397946B1 (en) 2013-11-05 2016-07-19 Cisco Technology, Inc. Forwarding to clusters of service nodes
US9674086B2 (en) 2013-11-05 2017-06-06 Cisco Technology, Inc. Work conserving schedular based on ranking
US10951522B2 (en) 2013-11-05 2021-03-16 Cisco Technology, Inc. IP-based forwarding of bridged and routed IP packets and unicast ARP
US9876711B2 (en) 2013-11-05 2018-01-23 Cisco Technology, Inc. Source address translation in overlay networks
US9374294B1 (en) 2013-11-05 2016-06-21 Cisco Technology, Inc. On-demand learning in overlay networks
US10778584B2 (en) 2013-11-05 2020-09-15 Cisco Technology, Inc. System and method for multi-path load balancing in network fabrics
US9502111B2 (en) 2013-11-05 2016-11-22 Cisco Technology, Inc. Weighted equal cost multipath routing
US9509092B2 (en) 2013-11-06 2016-11-29 Cisco Technology, Inc. System and apparatus for network device heat management
US10257099B2 (en) 2014-09-30 2019-04-09 A 10 Networks, Incorporated Applications of processing packets which contain geographic location information of the packet sender
US9762683B2 (en) * 2014-09-30 2017-09-12 A 10 Networks, Incorporated Use of packet header extension for geolocation/geotargeting
US10116493B2 (en) 2014-11-21 2018-10-30 Cisco Technology, Inc. Recovering from virtual port channel peer failure
FR3032035B1 (en) * 2015-01-27 2022-07-15 Arkema France TRANSPORTABLE DEVICE FOR ON-LINE MEASUREMENT OF THE HYDROGEN SULPHIDE CONCENTRATION OF A GAS EFFLUENT
US20160308786A1 (en) * 2015-04-17 2016-10-20 Futurewei Technologies, Inc. Temporal Tunnel Services
US10547543B2 (en) 2015-06-24 2020-01-28 Futurewei Technologies, Inc. Elegant temporal label switched path tunnel service controller
US10200280B2 (en) 2015-06-25 2019-02-05 Futurewei Technologies, Inc. Software-defined network for temporal label switched path tunnels
US10498640B2 (en) 2015-09-04 2019-12-03 Futurewei Technologies, Inc. PCE for temporal tunnel services
US10142163B2 (en) 2016-03-07 2018-11-27 Cisco Technology, Inc BFD over VxLAN on vPC uplinks
US10333828B2 (en) 2016-05-31 2019-06-25 Cisco Technology, Inc. Bidirectional multicasting over virtual port channel
FR3053194A1 (en) * 2016-06-22 2017-12-29 Orange METHOD AND DEVICE FOR PROVIDING AN ADDRESS BY A DEVICE MANAGING A NETWORK
US11509501B2 (en) 2016-07-20 2022-11-22 Cisco Technology, Inc. Automatic port verification and policy application for rogue devices
US10193750B2 (en) 2016-09-07 2019-01-29 Cisco Technology, Inc. Managing virtual port channel switch peers from software-defined network controller
US10432578B2 (en) 2016-09-27 2019-10-01 Cisco Technology, Inc. Client address based forwarding of dynamic host configuration protocol response packets
US10547509B2 (en) 2017-06-19 2020-01-28 Cisco Technology, Inc. Validation of a virtual port channel (VPC) endpoint in the network fabric
US10454882B2 (en) 2017-06-30 2019-10-22 Cisco Technology, Inc. DHCP in layer-3 overlay with anycast address support and network address transparency
US11012259B1 (en) * 2018-09-13 2021-05-18 Ca, Inc. Systems and methods for preserving system contextual information in an encapsulated packet

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1155319A (en) * 1997-08-07 1999-02-26 Hitachi Ltd Ipv4-ipv6 communication method and conversion device therefor
US6118784A (en) * 1996-11-01 2000-09-12 Hitachi, Ltd. Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus
JP2001274845A (en) * 2000-03-27 2001-10-05 Hitachi Ltd Communicating method accompanying protocol conversion and communication controller

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6690669B1 (en) * 1996-11-01 2004-02-10 Hitachi, Ltd. Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus
US7239618B1 (en) * 1998-12-11 2007-07-03 Lucent Technologies Inc. Single phase local mobility scheme for wireless access to packet-based networks
US20020019875A1 (en) * 2000-03-20 2002-02-14 Garrett John W. Service selection in a shared access network
JP2001326697A (en) * 2000-05-17 2001-11-22 Hitachi Ltd Mobile communication network, terminal, packet communication control method, and gateway unit
US20020087722A1 (en) * 2000-12-29 2002-07-04 Ragula Systems D/B/A/ Fatpipe Networks Domain name resolution making IP address selections in response to connection status when multiple connections are present
CA2435985C (en) * 2001-03-08 2009-10-13 British Telecommunications Public Limited Company Address translator
US7483697B2 (en) * 2001-03-13 2009-01-27 Nec Corporation System for managing mobile node in mobile network
KR100453050B1 (en) * 2002-05-29 2004-10-15 삼성전자주식회사 Method for communicating data between IPv4 and IPv6 and apparatus thereof
KR20050086925A (en) * 2002-12-20 2005-08-30 코닌클리케 필립스 일렉트로닉스 엔.브이. System and method for establishing communication between a client and a server in a heterogenous ip network
US7305481B2 (en) * 2003-01-07 2007-12-04 Hexago Inc. Connecting IPv6 devices through IPv4 network and network address translator (NAT) using tunnel setup protocol
US20040224681A1 (en) * 2003-02-27 2004-11-11 Interactive People Unplugged Ab Routed home network
US7149225B2 (en) * 2003-03-10 2006-12-12 Cisco Technology, Inc. Arrangement for traversing an IPv4 network by IPv6 mobile nodes via a mobility anchor point
US20050111380A1 (en) * 2003-11-25 2005-05-26 Farid Adrangi Method, apparatus and system for mobile nodes to dynamically discover configuration information
US7657642B2 (en) * 2003-12-22 2010-02-02 Hexago, Inc. IP network node and middleware for establishing connectivity to both the IPv4 and IPv6 networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6118784A (en) * 1996-11-01 2000-09-12 Hitachi, Ltd. Communicating method between IPv4 terminal and IPv6 terminal and IPv4-IPv6 converting apparatus
JPH1155319A (en) * 1997-08-07 1999-02-26 Hitachi Ltd Ipv4-ipv6 communication method and conversion device therefor
JP2001274845A (en) * 2000-03-27 2001-10-05 Hitachi Ltd Communicating method accompanying protocol conversion and communication controller

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7761553B2 (en) 2005-11-29 2010-07-20 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement in an access system
US9386047B2 (en) 2012-03-14 2016-07-05 Huawei Technologies Co., Ltd. Method, switch, server and system for sending connection establishment request

Also Published As

Publication number Publication date
TWI294732B (en) 2008-03-11
CN1922826A (en) 2007-02-28
KR20050079420A (en) 2005-08-10
US20050175020A1 (en) 2005-08-11
JP2007520970A (en) 2007-07-26
TW200537880A (en) 2005-11-16
EP1712044A1 (en) 2006-10-18
CN101321111A (en) 2008-12-10
US20080304501A1 (en) 2008-12-11

Similar Documents

Publication Publication Date Title
US20050175020A1 (en) Tunneling service method and system
US8130671B2 (en) Method and system for establishing bidirectional tunnel
EP2364543B1 (en) Broadband network access
US7616615B2 (en) Packet forwarding apparatus for connecting mobile terminal to ISP network
US7639686B2 (en) Access network clusterhead for providing local mobility management of a roaming IPv4 node
JP5495926B2 (en) Method of private addressing in proxy mobile IP network
KR100750370B1 (en) Address acquisition
JP4071136B2 (en) COMMUNICATION SYSTEM, CONNECTION DEVICE, AND COMMUNICATION METHOD
JP2006086800A (en) Communication apparatus for selecting source address
WO2003024056A2 (en) Addressing scheme for wireless mobile clients
WO2006132024A1 (en) Information processing server, remote control system, and remote control method
JP5147995B2 (en) Host identity protocol server address configuration
US7826410B2 (en) Method for updating DNS address in mobile IP terminal
US7173905B1 (en) PDSN fast tunnel lookup
JP2010062757A (en) Dns proxy apparatus and dns relay method
WO2015139397A1 (en) Nat64 resource acquisition method and acquisition/distribution apparatus
WO2011117959A1 (en) Communication apparatus, communication apparatus control method, and program
JP2006262352A (en) Mobile terminal, packet relay device, communication system, and communication method
Sun et al. DHCPv4-over-DHCPv6 (DHCP 4o6) transport
JP4242752B2 (en) Address table management method and terminal
JP2004007073A (en) Method for handover in radio communication and radio communication apparatus
JP2008244925A (en) Mobile communication system and mobile communication program
Holland RFC 8777: DNS Reverse IP Automatic Multicast Tunneling (AMT) Discovery
Dhanapal et al. AN OVERVIEW OF THE IPV6 ADDRESSING SCHEME
JP4429289B2 (en) Communication system, router, DHCP message rewriting method, and DHCP message rewriting program

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DPEN Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed from 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2005726912

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006552044

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWE Wipo information: entry into national phase

Ref document number: 200580006087.2

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 1014/MUMNP/2006

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2005726912

Country of ref document: EP