EP1653704B1 - Method and system for establishing a bidirectional tunnel - Google Patents
Method and system for establishing a bidirectional tunnel Download PDFInfo
- Publication number
- EP1653704B1 EP1653704B1 EP05256641A EP05256641A EP1653704B1 EP 1653704 B1 EP1653704 B1 EP 1653704B1 EP 05256641 A EP05256641 A EP 05256641A EP 05256641 A EP05256641 A EP 05256641A EP 1653704 B1 EP1653704 B1 EP 1653704B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- tunnel
- user node
- tep
- network
- teps
- 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.)
- Ceased
Links
- 238000000034 method Methods 0.000 title claims description 31
- 230000002457 bidirectional effect Effects 0.000 title description 15
- 238000004891 communication Methods 0.000 claims description 21
- 230000009977 dual effect Effects 0.000 claims description 7
- 230000004044 response Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 4
- 230000003068 static effect Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 230000005641 tunneling Effects 0.000 description 3
- 239000000284 extract Substances 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000007616 round robin method Methods 0.000 description 1
- 238000010187 selection method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- 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]
-
- 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/251—Translation of Internet protocol [IP] addresses between different IP versions
-
- 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/2542—Translation of Internet protocol [IP] addresses involving dual-stack hosts
-
- 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/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
- H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/167—Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
Definitions
- the present invention relates to tunnel service capable of data communication between different communication networks, and more particularly, to a method and system for establishing a bi-directional tunnel between a tunnel end point (TEP) and a user node which wish to communicate using Internet protocol version 6 (IPv6) in an Internet protocol version 4 (IPv4) network environment.
- TEP tunnel end point
- IPv6 Internet protocol version 6
- IPv4 Internet protocol version 4
- Internet communication networks may be based on IPv4 or IPv6.
- IPv4 is a network layer protocol that uses 32-bit Internet protocol (IP) addresses. As the number of addresses available is consumed by Internet users, an IPv4 address shortage appears to be inevitable in the long run.
- IPv6 which was called IP Next Generation (IPng), has been proposed by the Internet Engineering Task Force (IETF). IPv6 uses 128-bit Internet protocol addresses.
- IPng IP Next Generation
- IPv6 header allows extensions of the header region, so that the big drive for IPv6 is new uses, such as packet authenticity, data integrity extension, privacy extension, and so on.
- IPv4 and IPv6 are different protocols
- a bidirectional IPv6-over-IPv4 tunnel must be established using a TEP connected to both IPv4-based networks and IPv6-based networks.
- the bidirectional IPv6-over-IPv4 tunnel supports IPv6 connection in the IPv4-based network.
- the user node In order to establish the bidirectional IPv6-over-IPv4 tunnel, the user node needs network information such as the IPv4 address of the TEP and the IPv6 address of the user node, and the TEP needs network information such as the IPv4 address of the user node and the IPv6 address of the TEP.
- a user and TEP manager must exchange network information necessary for establishing the bidirectional IPv6-over-IPv4 tunnel by means of a phone call, messenger, email, advance notice, etc.
- the user and TEP manager manually establish the bidirectional IPv6-over-IPv4 tunnel using the exchanged network information.
- the user and TEP manager prepare a script using the network information, store the script as a file, and establish the bidirectional IPv6-over-IPv4 tunnel using the stored script file.
- the user and TEP manager when network information of the user node and TEP is changed, the user and TEP manager must manually establish the bidirectional IPv6-over-IPv4 tunnel using the changed network information. For example, when the user node moves to another network area, which causes a change in network information of the user node or the TEP, the user and TEP manager must manually establish the bidirectional IPv6-over-IPv4 tunnel.
- the TEP since the TEP is a service entity, the change in network information of a plurality of user nodes makes it difficult to provide the TEP manager with changed network information. The change in network information of the user node and the TEP makes it impossible for the user and TEP manager to grasp each other's network information, meaning that continuous tunneling service may not be provided to the user node.
- US 2004/0133692 discloses a method of setting up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across an IPv4 network.
- US 2004/0205233 discloses a push data system for pushing data to mobile communications devices.
- the present invention provides a method and system for establishing a bi-directional tunnel through direct communication between a tunnel end point (TEP) and a user node wishing to communicate using Internet protocol version 6 (IPv6) in an Internet protocol version 4 (IPv4) network environment.
- TEP tunnel end point
- IPv6 Internet protocol version 6
- IPv4 Internet protocol version 4
- the present invention also provides a method and system for establishing a bi-directional tunnel between the TEP and the user node in order to support mobility of the user node.
- the present invention also provides a method and system for establishing a bi-directional tunnel between the TEP and the user node in order to provide the user node with continuous tunneling service in spite of changes in network information of the user node and the TEP.
- the present invention also provides a method and system for establishing a bi-directional IPv6-over-IPv4 tunnel without user assistance.
- FIG. 1 is a diagram of a network to which a system for establishing a bi-directional tunnel is applied according to an embodiment of the present invention.
- the system establishes a bi-directional IPv6-over-IPv4 tunnel 125 for data communication between an IPv4/IPv6 user node 111 in an IPv4-only network 100 and an IPv6 user node 131 in an IPv6 network 130.
- the IPv4-based network 100 which is an IPv4-based Internet communication network, includes a plurality of IPv4 networks 110 and 120 shown in FIG. 1.
- the plurality of IPv4 networks 110 and 120 are different subnets, for IPv4 communication.
- the IPv4/IPv6 user node 111 and a tunnel end point (TEP) 121 are connected to the same IPv4-based network or different IPv4-based networks.
- TEP tunnel end point
- the IPv4 networks 110 includes the IPv4/IPv6 user node 111, a dynamic host configuration protocol (DHCP) server 112, and an IPv4 router 113.
- DHCP dynamic host configuration protocol
- the IPv4/IPv6 user node 111 may have a dual stack structure in order to store Internet protocol addresses. To be more specific, the IPv4/IPv6 user node 111 stores IPv4-based Internet protocol addresses (hereinafter referred to as "IPv4 addresses”) and IPv6-based Internet protocol addresses (hereinafter referred to as “IPv6 addresses”) in separate stacks, and uses an IPv4 address and IPv6 address as source addresses used to communicate data.
- IPv4 addresses IPv4-based Internet protocol addresses
- IPv6 addresses IPv6-based Internet protocol addresses
- the IPv4/IPv6 user node 111 may use a static IPv4 address or a dynamic IPv4 address. If the IPv4/IPv6 user node 111 uses the static address, the IPv4/IPv6 user node 111 disregards the dynamic IPv4 address allocated by the DHCP server 112. However, the IPv4/IPv6 user node 111 for which no static IPv4 address has been established uses the dynamic IPv4 address allocated to the IPv4/IPv6 user node 111 from the DHCP server 112.
- the IPv6 address is generated based on an IPv6 router advertisement (RA) message from the TEP 121 after the bidirectional tunnel is established.
- the IPv4/IPv6 user node 111 parses a prefix of the IPv6 RA message and performs an IPv6 address auto configuration process based on the parsing result to generate the IPv6 address.
- the IPv4/IPv6 user node 111 requests the DHCP server 112 for network information necessary for establishing the bi-directional IPv6-over-IPv4 tunnel 125.
- Network information includes an IPv4 address of the TEP 121. Therefore, a request for network information can be defined as a request for the IPv4 address of the TEP 121.
- the IPv4/IPv6 user node 111 receives network information including the IPv4 address of the TEP 121 from the DHCP server 112, and extracts the IPv4 address of the TEP 121 from the network information.
- the network information has a DHCP format. Therefore, the network information can be defined as a DHCP message.
- the IPv4/IPv6 user node 111 establishes a unidirectional tunnel from the IPv4/IPv6 user node 111 to the TEP 121 using the IPv4 address of the TEP 121.
- the IPv4/IPv6 user node 111 prepares a script using the IPv4 address of the TEP 121 extracted from the network information, and establishes the unidirectional tunnel using the script.
- the IPv4/IPv6 user node 111 sends a tunnel configuration request message to the TEP 121 via the IPv4 router 113 in order to establish the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111.
- the IPv4/IPv6 user node 111 can send the tunnel configuration request message using either transport control protocol (TCP), user datagram protocol (UDP), or Internet control message protocol (ICMP) according to an IPv4 network environment. If UDP is used to send the tunnel configuration request message, the IPv4/IPv6 user node 111 sends a UDP message as shown in FIG. 2 to the TEP 121.
- TCP transport control protocol
- UDP user datagram protocol
- ICMP Internet control message protocol
- the IPv4/IPv6 user node 111 When the IPv4/IPv6 user node 111 receives the IPv6 RA message from the TEP 121 after the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111 has been established, it performs the IPv6 address auto configuration process. To this end, the IPv4/IPv6 user node 111 includes an element (not shown) to perform the IPv6 address auto configuration process.
- the IPv6 address generated by the IPv6 address auto configuration process is referred to as a global IPv6 address of the IPv4/IPv6 user node 111. With the global IPv6 address generated, the bidirectional IPv6-over-IPv4 tunnel 125 is completely established.
- the IPv4/IPv6 user node 111 can normally communicate with the IPv6 user node 131 using IPv6.
- the IPv4/IPv6 user node 111 may be a mobile host such as a notebook computer or personal digital assistant (PDA), or a non-mobile host such as a desktop computer.
- a mobile host such as a notebook computer or personal digital assistant (PDA)
- PDA personal digital assistant
- the DHCP server 112 manages the IPv4 address of at least one TEP connected to the IPv4-only network 100 provided from an Internet service provider (ISP) (not shown), and provides the IPv4/IPv6 user node 111 with the DHCP message including the IPv4 address of at least one TEP at the request of the IPv4/IPv6 user node 111 for the network information or TEP address.
- ISP Internet service provider
- the IPv4 address of the TEP may be included in an option field of the DHCP message.
- a plurality of IPv4 addresses of the TEP may be included in the option field of the DHCP message. If the option field of the DHCP message includes a plurality of IPv4 addresses of the TEP, the IPv4/IPv6 user node 111 selects one of the plurality of IPv4 addresses of the TEP based on a predetermined selection method, for example, a round robin method.
- the IPv4 router 113 is a typical IPv4 router connecting the IPv4 network 110 and IPv4 network 120.
- the IPv4/IPv6 user node 111 establishes the IPv6-over-IPv4 tunnel 125 with the TEP 121 via the IPv4 router 113 as shown in FIG. 1.
- the IPv4/IPv6 user node 111 may establish the IPv6-over-IPv4 tunnel 125 via use a plurality of IPv4 routers that are not shown in FIG. 1.
- the TEP 121 When the TEP 121 receives the tunnel configuration request message from the IPv4/IPv6 user node 111, it authenticates the IPv4/IPv6 user node 111 using an ISP intrinsic protocol, and establishes the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111. When the TEP 121 establishes the unidirectional tunnel, it sends the IPv6 RA message to the IPv4/IPv6 user node 111 via the unidirectional tunnel. The bidirectional IPv6-over-IPv4 tunnel 125 between the TEP 121 and the IPv4/IPv6 user node 111 is established.
- the IPv4/IPv6 user node 111 can communicate IPv6 data with the IPv6 user node 131 via the TEP 121.
- the TEP 121 is referred to as a tunnel router.
- FIG. 3 is a block diagram of the IPv4/IPv6 user node 111 and TEP 121 shown in FIG. 1.
- the IPv4/IPv6 user node 111 includes a tunnel configuration agent 300, an IPv6 address auto configuration unit 320, a dual stack 330, and a communication processing unit 340.
- the tunnel configuration agent 300 includes a TEP address receiver 301, a tunnel configuration controller 302, a tunnel information handler 303, a tunnel configuration unit 304, a message creator & transmitter 305, and a UDP client 306.
- the TEP address receiver 301 extracts the IPv4 address of the TEP 121 from network information received from the DHCP server 112, and transmits the extracted IPv4 address to the tunnel configuration controller 302.
- the tunnel configuration controller 302 requests the IPv4 address of the TEP 121 or network information for establishing a tunnel to the DHCP server 112, controls the tunnel information handler 303 in order to establish a unidirectional tunnel from the IPv4/IPv6 user node 111 to TEP 121 using the IPv4 address of the TEP 121 received from the TEP address receiver 301, and controls the message creator & transmitter 305 in order to request the unidirectional tunnel and a unidirectional tunnel having the opposite direction to the unidirectional tunnel from the IPv4/IPv6 user node 111 to TEP 121 to be established.
- the tunnel configuration controller 302 provides an IPv4 address of the IPv4/IPv6 user node 111 that is included in network information received from the DHCP server 112 as a dual stack 330.
- the tunnel information handler 303 manages the IPv4 address of the TEP 121 provided by the tunnel configuration controller 302, and instructs the tunnel configuration unit 304 to establish the unidirectional tunnel from the IPv4/IPv6 user node 111 to the TEP 121. That is, the tunnel information handler 303 stores the IPv4 address of a TEP provided by the tunnel configuration controller 302, and, if each of IPv4 addresses of a plurality of TEPs is stored, can select one address based on a first in first out (FIFO) algorithm, for example.
- FIFO first in first out
- the tunnel configuration unit 304 prepares a script using an IPv4 address of the TEP 121 provided by the tunnel information handler 303, stores the script as a file, and establishes the unidirectional tunnel from the IPv4/IPv6 user node 111 to the TEP 121 using the script file.
- the message creator & transmitter 305 creates a unidirectional tunnel configuration request message to be sent to the TEP 121 controlled by the tunnel configuration controller 302.
- the tunnel configuration request message is a packet having a format suitable for TCP, UDP, or ICMP.
- the tunnel configuration agent 300 transmits the tunnel configuration request message using UDP.
- the message creator & transmitter 305 can create a packet having a UDP format as shown in FIG. 2.
- the message creator & transmitter 305 transmits the message to the UDP client 306.
- the message creator & transmitter 305 receives the message from the TEP 121 from the UDP client 306 and transmits it to the tunnel configuration controller 302.
- the message from the TEP 121 may include a tunnel configuration complete message or a tunnel configuration failure message.
- the UDP client 306 transmits a UDP packet received from the message creator & transmitter 305 for a tunnel configuration request to the TEP 121, and the message received from the TEP 121, to the message creator & transmitter 305.
- the message creator & transmitter 305 and the UDP client 306 communicate data between the TEP 121 and the IPv4/IPv6 user node 111 in order to establish the bi-directional IPv6-over-IPv4 tunnel 125.
- the tunnel configuration complete message or tunnel configuration failure message received from the TEP 121 is provided to the tunnel configuration controller 302 via the message creator & transmitter 305 and UDP client 306.
- the tunnel configuration controller 302 analyzes the tunnel configuration failure message and informs a user of a tunnel configuration failure, or controls the tunnel information handler 303 using another IPv4 address of another TEP to retry tunnel configuration establishment.
- the communication processing unit 350 of the TEP 121 broadcasts the IPv6 RA message.
- the communication processing unit 340 of the IPv4/IPv6 user node 111 receives the IPv6 RA message.
- the communication processing units 340 and 350 that a socket for data communication of IPv6 between the IPv4/IPv6 user node 111 and the IPv6 user node 131 relating to the IPv6-over-IPv4 tunnel 125 make it possible to transmit and receive a packet with layer 2 (L2) level between the TEP 121 and the IPv4/IPv6 user node 111.
- the communication processing unit 340 receives the IPv6 RA message to transmit it to the IPv6 address auto configuration unit 320 in order to allow the IPv6 address of the IPv4/IPv6 user node 111 to be automatically generated.
- the IPv6 address auto configuration unit 320 receives the IPv6 RA message from the communication processing unit 340 and automatically generates the IPv6 address of the IPv4/IPv6 user node 111 based on a prefix of the IPv6 RA message.
- the generated IPv6 address is provided to the dual stack 330.
- the dual stack 330 stores the IPv4 address of the IPv4/IPv6 user node 111 provided by the tunnel configuration agent 300 and IPv6 address provided by the IPv6 address auto configuration unit 320 in separate stack. If the static IPv4 address is stored in the dual stack 330, it disregards the IPv4 address of the IPv4/IPv6 user node 111 provided by the tunnel configuration agent 300.
- the TEP 121 includes a tunnel configuration agent 310 and the communication processing unit 350.
- the tunnel configuration agent 310 includes a tunnel configuration controller 311, a message parser 312, a tunnel information handler 313, a UDP port 314, and a tunnel configuration unit 315.
- the tunnel configuration controller 311 controls the message parser 312 and tunnel information handler 313 in order to establish the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111.
- the message parser 312 parses the UDP packet received via the UDP port 314, and transmits the parsed UDP packet to the tunnel configuration controller 311.
- the tunnel configuration controller 311 receives the tunnel configuration request message transmitted from the IPv4/IPv6 user node 111.
- the UDP port 314 receives the UDP packet transmitted from the IPv4/IPv6 user node 111, and transmits the UDP packet to the IPv4/IPv6 user node 111.
- the UDP port 314 is previously placed in standby in order to receive the UDP packet, which has the same format as shown in FIG. 2.
- the UDP packet defines a message field based on previously defined code information in order to determine its use.
- the UDP packet when a UDP packet transmitted from the UDP port 314 to the UDP client 306 defines the message field (message region in FIG. 2) as "01", the UDP packet is a tunnel configuration request message; when a UDP packet defines the message field as "EE”, the UDP packet is a tunnel terminating request message; when a UDP packet defines the message field as "77”, the UDP packet is a tunnel configuration OK message; when a UDP packet defines the message field as "FF”, the UDP packet is a tunnel configuration failure message due to a full slot of the TEP 121; when a UDP packet defines the message field as "F0”, the UDP packet is a tunnel configuration failure message that requests a tunnel configuration again; when a UDP packet defines the message field as "FA”, the UDP packet is a tunnel configuration failure message that indicates service unavailability; when a UDP packet defines the message field as "FD”, the UDP packet is a tunnel configuration failure message that does not allow a tunnel configuration for the IPv4/IPv6
- the UDP packet is configured based on the previously defined code information (01, EE, FF, ...) according to the type of the UDP packet.
- the tunnel configuration OK message and tunnel configuration failure message are included in the tunnel configuration response message transmitted from the TEP 121 to the IPv4/IPv6 user node 111.
- the tunnel information handler 313 stores the IPv4 address of the IPv4/IPv6 user node 111 provided by the tunnel configuration controller 311, and requests the tunnel configuration unit 315 to establish the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111.
- the tunnel configuration unit 315 establishes the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111 using the IPv4 address of the IPv4/IPv6 user node 111 provided by the tunnel information handler 313.
- the tunnel configuration unit 315 confirms the unidirectional tunnel establishment from the TEP 121 to the IPv4/IPv6 user node 111 via the UDP port 314.
- the tunnel configuration agents 300 and 310 transmit a packet using UDP.
- the message creator & transmitter 305, UDP client 306, the UDP port 314, and message parser 312 are designed and configured to transmit the packet between the IPv4/IPv6 user node 111 and the TEP 121 using either TCP, UDP, or ICMP.
- the tunnel configuration agent 310 further includes a TCP port for TCP communication to confirm tunnel configuration via the TCP port, or establishes an interusable type for ICMP communication to confirm tunnel configuration.
- the tunnel configuration agent 300 is designed to transmit a message having a format corresponding to the tunnel configuration agent 310.
- the communication processing unit 350 sends the IPv6 RA message to the IPv4/IPv6 user node 111.
- the IPv4/IPv6 user node 111 generates the IPv6 address using the IPv6 RA message to establish the bidirectional IPv6-over-IPv4 tunnel 125 between the TEP 121 and the IPv4/IPv6 user node 111, and communicates with the IPv6 user node 131 using IPv6 via the TEP 121.
- the IPv6 user node 131 having an IPv6 function may be a mobile host or non-mobile host.
- FIG. 4 is a screen showing the IPv4/IPv6 user node 111 establishing the bi-directional tunnel by the tunnel configuration agent 300 for IPv6 communication after connecting to a new IPv4 network.
- FIG. 4 shows that no user configuration control is necessary to establish the bi-directional tunnel.
- FIG. 5 is a flowchart describing a method of establishing a bi-directional tunnel according to an embodiment of the present invention. The flowchart will be described with reference to FIG. 1.
- the IPv4/IPv6 user node 111 connects to a new IPv4 network and sends a TEP address request message to the DHCP server 112 (Operation 501).
- the message which requires network information necessary for establishing the bi-directional tunnel between TEP 121 and IPv4/IPv6 user node 111, may be DHCP-DISCOVER or DHCP-REQUEST. If the IPv4 network has a plurality of DHCP servers, the IPv4/IPv6 user node 111 selects one DHCP server and sends the TEP address request message to the selected DHCP server.
- the DHCP server 112 provides the IPv4/IPv6 user node 111 with a DHCP message including an IPv4 address of the IPv4/IPv6 user node 111 and an IPv4 address of the TEP 121 as a TEP address response (Operation 502), which may be DHCP OFFER, DHCP ACK, or network information response.
- the TEP address response may include IPv4 addresses of a plurality of TEPs.
- the plurality of TEPs are tunnel routers connected to the IPv4-only network 100 and IPv6 network 130.
- the DHCP message includes the IPv4 address of the IPv4/IPv6 user node 111.
- the IPv4/IPv6 user node 111 receives the TEP address response, establishes the unidirectional tunnel from the IPv4/IPv6 user node 111 to the TEP 121 using the IPv4 address of the IPv4/IPv6 user node 111 and the IPv4 address of the TEP 121 (Operation 503).
- the tunnel configuration agent 300 installed in the IPv4/IPv6 user node 111 establishes the unidirectional tunnel.
- the IPv4/IPv6 user node 111 sends a tunnel configuration request message to the TEP 121 (Operation 504).
- the tunnel configuration request message may be transmitted as a UDP packet. If the tunnel configuration request message is a UDP packet, the tunnel configuration request message may be UDP Request, while it is transmitted using either TCP, UDP, or ICMP.
- the TEP 121 receives the tunnel configuration request message and establishes the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111 (Operation 505). That is, the TEP 121 parses the received tunnel configuration request message to extract the IPv4 address of the IPv4/IPv6 user node 111 and establish the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111 using the extracted the IPv4 address of the IPv4/IPv6 user node 111 and the IPv4 address of the TEP 121.
- the TEP 121 establishes the unidirectional tunnel and sends a tunnel configuration response message indicating that the unidirectional tunnel has been completely established to the IPv4/IPv6 user node 111 (Operation 506).
- the TEP 121 transmits an RA message of the IPv6 network required to be communicated by the IPv4/IPv6 user node 111 to the IPv4/IPv6 user node 111 (Operation 507).
- the IPv4/IPv6 user node 111 automatically establishes the IPv6 address of the IPv4/IPv6 user node 111 based on a prefix of the IPv6 RA message.
- the bidirectional IPv6-over-IPv4 tunnel 125 between the TEP 121 and the IPv4/IPv6 user node 111 is established (Operation 509) so that the IPv4/IPv6 user node 111 communicates with the IPv6 used node 131 using IPv6 (Operation 510).
- FIG. 6 is a flowchart describing a method of establishing a bi-directional tunnel according to another embodiment of the present invention.
- Operations 601 to 604 of FIG. 6 are the same as Operations 501 to 504 of FIG. 5, and Operations 608 to 613 of FIG. 6 are the same as Operations 504 to 510 of FIG. 5, and therefore these operations will not be described again.
- TEP 121 fails to establish the unidirectional tunnel from the TEP 121 to the IPv4/IPv6 user node 111, another TEP is used to establish the unidirectional tunnel.
- a first TEP corresponding to the TEP 121 of FIG. 5 and a second TEP corresponding to another TEP are shown in FIG. 6.
- the IPv4/IPv6 user node 111 requests the first TEP to establish the unidirectional tunnel. However, since the fist TEP fails to establish the unidirectional tunnel (Operation 605), it sends a tunnel configuration response message that indicates failure in establishing the unidirectional tunnel to the IPv4/IPv6 user node 111 (Operation 606). There are several reasons that the fist TEP can fail to establish the unidirectional tunnel. The reasons are described in code information defined in a message region with reference to FIG. 2.
- the IPv4/IPv6 user node 111 receives the tunnel configuration response message that indicates failure in establishing the unidirectional tunnel from the first TEP and informs a user of the tunnel configuration failure (Operation 607).
- the IPv4/IPv6 user node 111 sends a tunnel configuration request message using an IPv4 address of a TEP other than the first TEP of those received from the DHCP server 112 (Operation 608). If the IPv4 address is the IPv4 address of the second TEP, the IPv4/IPv6 user node 111 can send the tunnel configuration request message to the second TEP.
- the IPv4/IPv6 user node 111 sends the tunnel configuration request message to the first TEP again.
- the second TEP establishes the unidirectional tunnel as described in the TEP 121 of FIG. 5 (Operation 609).
- the bi-directional tunnel between a user node and a TEP is automatically established without user assistance, so that the tunneling service is continuously provided to the user node in spite of changes in a network connected to the user node.
- the user node in a mobile IPv4 network environment can be continuously connected to an IPv6 network according to the method of establishing the bidirectional tunnel.
- the user is not required to know TEP information of a new network, and a TEP manager is not required to know information of changed user nodes.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
- The present invention relates to tunnel service capable of data communication between different communication networks, and more particularly, to a method and system for establishing a bi-directional tunnel between a tunnel end point (TEP) and a user node which wish to communicate using Internet protocol version 6 (IPv6) in an Internet protocol version 4 (IPv4) network environment.
- Internet communication networks may be based on IPv4 or IPv6.
- IPv4 is a network layer protocol that uses 32-bit Internet protocol (IP) addresses. As the number of addresses available is consumed by Internet users, an IPv4 address shortage appears to be inevitable in the long run. To solve the IPv4 address shortage, IPv6, which was called IP Next Generation (IPng), has been proposed by the Internet Engineering Task Force (IETF). IPv6 uses 128-bit Internet protocol addresses. An IPv6 header allows extensions of the header region, so that the big drive for IPv6 is new uses, such as packet authenticity, data integrity extension, privacy extension, and so on.
- Since IPv4 and IPv6 are different protocols, when a user node connected to the IPv4-based network wishes to use IPv6 communication, a bidirectional IPv6-over-IPv4 tunnel must be established using a TEP connected to both IPv4-based networks and IPv6-based networks. The bidirectional IPv6-over-IPv4 tunnel supports IPv6 connection in the IPv4-based network.
- In order to establish the bidirectional IPv6-over-IPv4 tunnel, the user node needs network information such as the IPv4 address of the TEP and the IPv6 address of the user node, and the TEP needs network information such as the IPv4 address of the user node and the IPv6 address of the TEP.
- However, since existing networks spontaneously do not provide network information, a user and TEP manager must exchange network information necessary for establishing the bidirectional IPv6-over-IPv4 tunnel by means of a phone call, messenger, email, advance notice, etc. The user and TEP manager manually establish the bidirectional IPv6-over-IPv4 tunnel using the exchanged network information. For example, the user and TEP manager prepare a script using the network information, store the script as a file, and establish the bidirectional IPv6-over-IPv4 tunnel using the stored script file.
- Therefore, when network information of the user node and TEP is changed, the user and TEP manager must manually establish the bidirectional IPv6-over-IPv4 tunnel using the changed network information. For example, when the user node moves to another network area, which causes a change in network information of the user node or the TEP, the user and TEP manager must manually establish the bidirectional IPv6-over-IPv4 tunnel. However, since the TEP is a service entity, the change in network information of a plurality of user nodes makes it difficult to provide the TEP manager with changed network information. The change in network information of the user node and the TEP makes it impossible for the user and TEP manager to grasp each other's network information, meaning that continuous tunneling service may not be provided to the user node.
-
US 2004/0133692 discloses a method of setting up IPv6-in-IPv4 networks to permit IPv6 nodes to communicate across an IPv4 network. -
US 2004/0205233 discloses a push data system for pushing data to mobile communications devices. - According to the present invention there is provided an apparatus and method as set forth in the appended claims. Preferred features of the invention will be apparent from the dependent claims, and the description which follows.
- Additional aspects and/or advantages of the invention will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the invention.
- The present invention provides a method and system for establishing a bi-directional tunnel through direct communication between a tunnel end point (TEP) and a user node wishing to communicate using Internet protocol version 6 (IPv6) in an Internet protocol version 4 (IPv4) network environment.
- The present invention also provides a method and system for establishing a bi-directional tunnel between the TEP and the user node in order to support mobility of the user node.
- The present invention also provides a method and system for establishing a bi-directional tunnel between the TEP and the user node in order to provide the user node with continuous tunneling service in spite of changes in network information of the user node and the TEP.
- The present invention also provides a method and system for establishing a bi-directional IPv6-over-IPv4 tunnel without user assistance.
- For a better understanding of the invention, and to show how embodiments of the same may be carried into effect, reference will now be made, by way of example, to the accompanying diagrammatic drawings in which:
- FIG. 1 is a diagram of a network to which a system for establishing a bi-directional tunnel is applied according to an embodiment of the present invention;
- FIG. 2 is a structural diagram of a User Datagram Protocol (UDP) message sent by an IPv4/IPv6 user node to a tunnel end point (TEP) shown in FIG. 1;
- FIG. 3 is a block diagram of the IPv4/IPv6 user node and TEP shown in FIG. 1;
- FIG. 4 is a screen showing the IPv4/IPv6 user node establishing the bi-directional tunnel in a new network;
- FIG. 5 is a flowchart describing a method of establishing a bi-directional tunnel according to an embodiment of the present invention; and
- FIG. 6 is a flowchart describing a method of establishing a bi-directional tunnel according to another embodiment of the present invention.
- 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.
- The present invention will now be described more fully with reference to the accompanying drawings, in which preferred embodiments of the invention are shown.
- FIG. 1 is a diagram of a network to which a system for establishing a bi-directional tunnel is applied according to an embodiment of the present invention.
- Referring to FIG. 1, the system establishes a bi-directional IPv6-over-IPv4
tunnel 125 for data communication between an IPv4/IPv6 user node 111 in an IPv4-only network 100 and anIPv6 user node 131 in anIPv6 network 130. - The IPv4-based
network 100, which is an IPv4-based Internet communication network, includes a plurality ofIPv4 networks IPv4 networks IPv6 user node 111 and a tunnel end point (TEP) 121 are connected to the same IPv4-based network or different IPv4-based networks. - The
IPv4 networks 110 includes the IPv4/IPv6 user node 111, a dynamic host configuration protocol (DHCP)server 112, and anIPv4 router 113. - The IPv4/
IPv6 user node 111 may have a dual stack structure in order to store Internet protocol addresses. To be more specific, the IPv4/IPv6 user node 111 stores IPv4-based Internet protocol addresses (hereinafter referred to as "IPv4 addresses") and IPv6-based Internet protocol addresses (hereinafter referred to as "IPv6 addresses") in separate stacks, and uses an IPv4 address and IPv6 address as source addresses used to communicate data. - The IPv4/
IPv6 user node 111 may use a static IPv4 address or a dynamic IPv4 address. If the IPv4/IPv6 user node 111 uses the static address, the IPv4/IPv6 user node 111 disregards the dynamic IPv4 address allocated by theDHCP server 112. However, the IPv4/IPv6 user node 111 for which no static IPv4 address has been established uses the dynamic IPv4 address allocated to the IPv4/IPv6 user node 111 from theDHCP server 112. - The IPv6 address is generated based on an IPv6 router advertisement (RA) message from the
TEP 121 after the bidirectional tunnel is established. The IPv4/IPv6 user node 111 parses a prefix of the IPv6 RA message and performs an IPv6 address auto configuration process based on the parsing result to generate the IPv6 address. - The IPv4/
IPv6 user node 111 requests theDHCP server 112 for network information necessary for establishing the bi-directional IPv6-over-IPv4tunnel 125. Network information includes an IPv4 address of theTEP 121. Therefore, a request for network information can be defined as a request for the IPv4 address of theTEP 121. - The IPv4/
IPv6 user node 111 receives network information including the IPv4 address of theTEP 121 from theDHCP server 112, and extracts the IPv4 address of theTEP 121 from the network information. The network information has a DHCP format. Therefore, the network information can be defined as a DHCP message. - The IPv4/
IPv6 user node 111 establishes a unidirectional tunnel from the IPv4/IPv6 user node 111 to theTEP 121 using the IPv4 address of theTEP 121. For example, the IPv4/IPv6 user node 111 prepares a script using the IPv4 address of theTEP 121 extracted from the network information, and establishes the unidirectional tunnel using the script. - The IPv4/
IPv6 user node 111 sends a tunnel configuration request message to theTEP 121 via theIPv4 router 113 in order to establish the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111. The IPv4/IPv6 user node 111 can send the tunnel configuration request message using either transport control protocol (TCP), user datagram protocol (UDP), or Internet control message protocol (ICMP) according to an IPv4 network environment. If UDP is used to send the tunnel configuration request message, the IPv4/IPv6 user node 111 sends a UDP message as shown in FIG. 2 to theTEP 121. - When the IPv4/
IPv6 user node 111 receives the IPv6 RA message from theTEP 121 after the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111 has been established, it performs the IPv6 address auto configuration process. To this end, the IPv4/IPv6 user node 111 includes an element (not shown) to perform the IPv6 address auto configuration process. The IPv6 address generated by the IPv6 address auto configuration process is referred to as a global IPv6 address of the IPv4/IPv6 user node 111. With the global IPv6 address generated, the bidirectional IPv6-over-IPv4tunnel 125 is completely established. The IPv4/IPv6 user node 111 can normally communicate with theIPv6 user node 131 using IPv6. - The IPv4/
IPv6 user node 111 may be a mobile host such as a notebook computer or personal digital assistant (PDA), or a non-mobile host such as a desktop computer. - The
DHCP server 112 manages the IPv4 address of at least one TEP connected to the IPv4-only network 100 provided from an Internet service provider (ISP) (not shown), and provides the IPv4/IPv6 user node 111 with the DHCP message including the IPv4 address of at least one TEP at the request of the IPv4/IPv6 user node 111 for the network information or TEP address. - The IPv4 address of the TEP may be included in an option field of the DHCP message. A plurality of IPv4 addresses of the TEP may be included in the option field of the DHCP message. If the option field of the DHCP message includes a plurality of IPv4 addresses of the TEP, the IPv4/
IPv6 user node 111 selects one of the plurality of IPv4 addresses of the TEP based on a predetermined selection method, for example, a round robin method. - The
IPv4 router 113 is a typical IPv4 router connecting theIPv4 network 110 andIPv4 network 120. The IPv4/IPv6 user node 111 establishes the IPv6-over-IPv4 tunnel 125 with theTEP 121 via theIPv4 router 113 as shown in FIG. 1. However, the IPv4/IPv6 user node 111 may establish the IPv6-over-IPv4 tunnel 125 via use a plurality of IPv4 routers that are not shown in FIG. 1. - When the
TEP 121 receives the tunnel configuration request message from the IPv4/IPv6 user node 111, it authenticates the IPv4/IPv6 user node 111 using an ISP intrinsic protocol, and establishes the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111. When theTEP 121 establishes the unidirectional tunnel, it sends the IPv6 RA message to the IPv4/IPv6 user node 111 via the unidirectional tunnel. The bidirectional IPv6-over-IPv4 tunnel 125 between theTEP 121 and the IPv4/IPv6 user node 111 is established. - The IPv4/
IPv6 user node 111 can communicate IPv6 data with theIPv6 user node 131 via theTEP 121. TheTEP 121 is referred to as a tunnel router. - The IPv4/
IPv6 user node 111 andTEP 121 are configured as shown in FIG. 3. FIG. 3 is a block diagram of the IPv4/IPv6 user node 111 andTEP 121 shown in FIG. 1. Referring to FIG. 3, the IPv4/IPv6 user node 111 includes atunnel configuration agent 300, an IPv6 addressauto configuration unit 320,adual stack 330, and acommunication processing unit 340. - The
tunnel configuration agent 300 includes aTEP address receiver 301, atunnel configuration controller 302, atunnel information handler 303, atunnel configuration unit 304, a message creator &transmitter 305, and aUDP client 306. - The
TEP address receiver 301 extracts the IPv4 address of theTEP 121 from network information received from theDHCP server 112, and transmits the extracted IPv4 address to thetunnel configuration controller 302. - The
tunnel configuration controller 302 requests the IPv4 address of theTEP 121 or network information for establishing a tunnel to theDHCP server 112, controls thetunnel information handler 303 in order to establish a unidirectional tunnel from the IPv4/IPv6 user node 111 toTEP 121 using the IPv4 address of theTEP 121 received from theTEP address receiver 301, and controls the message creator &transmitter 305 in order to request the unidirectional tunnel and a unidirectional tunnel having the opposite direction to the unidirectional tunnel from the IPv4/IPv6 user node 111 toTEP 121 to be established. Thetunnel configuration controller 302 provides an IPv4 address of the IPv4/IPv6 user node 111 that is included in network information received from theDHCP server 112 as adual stack 330. - The
tunnel information handler 303 manages the IPv4 address of theTEP 121 provided by thetunnel configuration controller 302, and instructs thetunnel configuration unit 304 to establish the unidirectional tunnel from the IPv4/IPv6 user node 111 to theTEP 121. That is, thetunnel information handler 303 stores the IPv4 address of a TEP provided by thetunnel configuration controller 302, and, if each of IPv4 addresses of a plurality of TEPs is stored, can select one address based on a first in first out (FIFO) algorithm, for example. - The
tunnel configuration unit 304 prepares a script using an IPv4 address of theTEP 121 provided by thetunnel information handler 303, stores the script as a file, and establishes the unidirectional tunnel from the IPv4/IPv6 user node 111 to theTEP 121 using the script file. - The message creator &
transmitter 305 creates a unidirectional tunnel configuration request message to be sent to theTEP 121 controlled by thetunnel configuration controller 302. The tunnel configuration request message is a packet having a format suitable for TCP, UDP, or ICMP. Thetunnel configuration agent 300 transmits the tunnel configuration request message using UDP. The message creator &transmitter 305 can create a packet having a UDP format as shown in FIG. 2. The message creator &transmitter 305 transmits the message to theUDP client 306. - The message creator &
transmitter 305 receives the message from theTEP 121 from theUDP client 306 and transmits it to thetunnel configuration controller 302. The message from theTEP 121 may include a tunnel configuration complete message or a tunnel configuration failure message. - The
UDP client 306 transmits a UDP packet received from the message creator &transmitter 305 for a tunnel configuration request to theTEP 121, and the message received from theTEP 121, to the message creator &transmitter 305. - The message creator &
transmitter 305 and theUDP client 306 communicate data between theTEP 121 and the IPv4/IPv6 user node 111 in order to establish the bi-directional IPv6-over-IPv4 tunnel 125. - The tunnel configuration complete message or tunnel configuration failure message received from the
TEP 121 is provided to thetunnel configuration controller 302 via the message creator &transmitter 305 andUDP client 306. Thetunnel configuration controller 302 analyzes the tunnel configuration failure message and informs a user of a tunnel configuration failure, or controls thetunnel information handler 303 using another IPv4 address of another TEP to retry tunnel configuration establishment. - When the uni-directional IPv6-
over-IPv4 tunnel 125 from theTEP 121 to the IPv4/IPv6 user node 111 is established, thecommunication processing unit 350 of theTEP 121 broadcasts the IPv6 RA message. Thecommunication processing unit 340 of the IPv4/IPv6 user node 111 receives the IPv6 RA message. - The
communication processing units IPv6 user node 111 and theIPv6 user node 131 relating to the IPv6-over-IPv4 tunnel 125 make it possible to transmit and receive a packet with layer 2 (L2) level between theTEP 121 and the IPv4/IPv6 user node 111. Thecommunication processing unit 340 receives the IPv6 RA message to transmit it to the IPv6 addressauto configuration unit 320 in order to allow the IPv6 address of the IPv4/IPv6 user node 111 to be automatically generated. - The IPv6 address
auto configuration unit 320 receives the IPv6 RA message from thecommunication processing unit 340 and automatically generates the IPv6 address of the IPv4/IPv6 user node 111 based on a prefix of the IPv6 RA message. The generated IPv6 address is provided to thedual stack 330. - The
dual stack 330 stores the IPv4 address of the IPv4/IPv6 user node 111 provided by thetunnel configuration agent 300 and IPv6 address provided by the IPv6 addressauto configuration unit 320 in separate stack. If the static IPv4 address is stored in thedual stack 330, it disregards the IPv4 address of the IPv4/IPv6 user node 111 provided by thetunnel configuration agent 300. - The
TEP 121 includes atunnel configuration agent 310 and thecommunication processing unit 350. Thetunnel configuration agent 310 includes atunnel configuration controller 311, amessage parser 312, atunnel information handler 313, aUDP port 314, and atunnel configuration unit 315. - The
tunnel configuration controller 311 controls themessage parser 312 andtunnel information handler 313 in order to establish the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111. - The
message parser 312 parses the UDP packet received via theUDP port 314, and transmits the parsed UDP packet to thetunnel configuration controller 311. Thetunnel configuration controller 311 receives the tunnel configuration request message transmitted from the IPv4/IPv6 user node 111. - The
UDP port 314 receives the UDP packet transmitted from the IPv4/IPv6 user node 111, and transmits the UDP packet to the IPv4/IPv6 user node 111. theUDP port 314 is previously placed in standby in order to receive the UDP packet, which has the same format as shown in FIG. 2. The UDP packet defines a message field based on previously defined code information in order to determine its use. - For example, when a UDP packet transmitted from the
UDP port 314 to theUDP client 306 defines the message field (message region in FIG. 2) as "01", the UDP packet is a tunnel configuration request message; when a UDP packet defines the message field as "EE", the UDP packet is a tunnel terminating request message; when a UDP packet defines the message field as "77", the UDP packet is a tunnel configuration OK message; when a UDP packet defines the message field as "FF", the UDP packet is a tunnel configuration failure message due to a full slot of theTEP 121; when a UDP packet defines the message field as "F0", the UDP packet is a tunnel configuration failure message that requests a tunnel configuration again; when a UDP packet defines the message field as "FA", the UDP packet is a tunnel configuration failure message that indicates service unavailability; when a UDP packet defines the message field as "FD", the UDP packet is a tunnel configuration failure message that does not allow a tunnel configuration for the IPv4/IPv6 user node 111; and when a UDP packet defines the message field as "94", the UDP packet is a tunnel configuration failure message that indicates service unavailability while recommending another TEP. The UDP packet is configured based on the previously defined code information (01, EE, FF, ...) according to the type of the UDP packet. The tunnel configuration OK message and tunnel configuration failure message are included in the tunnel configuration response message transmitted from theTEP 121 to the IPv4/IPv6 user node 111. - The
tunnel information handler 313 stores the IPv4 address of the IPv4/IPv6 user node 111 provided by thetunnel configuration controller 311, and requests thetunnel configuration unit 315 to establish the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111. - The
tunnel configuration unit 315 establishes the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111 using the IPv4 address of the IPv4/IPv6 user node 111 provided by thetunnel information handler 313. Thetunnel configuration unit 315 confirms the unidirectional tunnel establishment from theTEP 121 to the IPv4/IPv6 user node 111 via theUDP port 314. - The
tunnel configuration agents transmitter 305,UDP client 306, theUDP port 314, andmessage parser 312 are designed and configured to transmit the packet between the IPv4/IPv6 user node 111 and theTEP 121 using either TCP, UDP, or ICMP. For example, thetunnel configuration agent 310 further includes a TCP port for TCP communication to confirm tunnel configuration via the TCP port, or establishes an interusable type for ICMP communication to confirm tunnel configuration. Thetunnel configuration agent 300 is designed to transmit a message having a format corresponding to thetunnel configuration agent 310. - When a tunnel from the
TEP 121 to the IPv4/IPv6 user node 111 is established, thecommunication processing unit 350 sends the IPv6 RA message to the IPv4/IPv6 user node 111. The IPv4/IPv6 user node 111 generates the IPv6 address using the IPv6 RA message to establish the bidirectional IPv6-over-IPv4 tunnel 125 between theTEP 121 and the IPv4/IPv6 user node 111, and communicates with theIPv6 user node 131 using IPv6 via theTEP 121. TheIPv6 user node 131 having an IPv6 function may be a mobile host or non-mobile host. - FIG. 4 is a screen showing the IPv4/
IPv6 user node 111 establishing the bi-directional tunnel by thetunnel configuration agent 300 for IPv6 communication after connecting to a new IPv4 network. FIG. 4 shows that no user configuration control is necessary to establish the bi-directional tunnel. - FIG. 5 is a flowchart describing a method of establishing a bi-directional tunnel according to an embodiment of the present invention. The flowchart will be described with reference to FIG. 1.
- The IPv4/
IPv6 user node 111 connects to a new IPv4 network and sends a TEP address request message to the DHCP server 112 (Operation 501). The message, which requires network information necessary for establishing the bi-directional tunnel betweenTEP 121 and IPv4/IPv6 user node 111, may be DHCP-DISCOVER or DHCP-REQUEST. If the IPv4 network has a plurality of DHCP servers, the IPv4/IPv6 user node 111 selects one DHCP server and sends the TEP address request message to the selected DHCP server. - The
DHCP server 112 provides the IPv4/IPv6 user node 111 with a DHCP message including an IPv4 address of the IPv4/IPv6 user node 111 and an IPv4 address of theTEP 121 as a TEP address response (Operation 502), which may be DHCP OFFER, DHCP ACK, or network information response. The TEP address response may include IPv4 addresses of a plurality of TEPs. The plurality of TEPs are tunnel routers connected to the IPv4-only network 100 andIPv6 network 130. The DHCP message includes the IPv4 address of the IPv4/IPv6 user node 111. - The IPv4/
IPv6 user node 111 receives the TEP address response, establishes the unidirectional tunnel from the IPv4/IPv6 user node 111 to theTEP 121 using the IPv4 address of the IPv4/IPv6 user node 111 and the IPv4 address of the TEP 121 (Operation 503). Thetunnel configuration agent 300 installed in the IPv4/IPv6 user node 111 establishes the unidirectional tunnel. - The IPv4/
IPv6 user node 111 sends a tunnel configuration request message to the TEP 121 (Operation 504). The tunnel configuration request message may be transmitted as a UDP packet. If the tunnel configuration request message is a UDP packet, the tunnel configuration request message may be UDP Request, while it is transmitted using either TCP, UDP, or ICMP. - The
TEP 121 receives the tunnel configuration request message and establishes the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111 (Operation 505). That is, theTEP 121 parses the received tunnel configuration request message to extract the IPv4 address of the IPv4/IPv6 user node 111 and establish the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111 using the extracted the IPv4 address of the IPv4/IPv6 user node 111 and the IPv4 address of theTEP 121. - The
TEP 121 establishes the unidirectional tunnel and sends a tunnel configuration response message indicating that the unidirectional tunnel has been completely established to the IPv4/IPv6 user node 111 (Operation 506). - The
TEP 121 transmits an RA message of the IPv6 network required to be communicated by the IPv4/IPv6 user node 111 to the IPv4/IPv6 user node 111 (Operation 507). The IPv4/IPv6 user node 111 automatically establishes the IPv6 address of the IPv4/IPv6 user node 111 based on a prefix of the IPv6 RA message. The bidirectional IPv6-over-IPv4 tunnel 125 between theTEP 121 and the IPv4/IPv6 user node 111 is established (Operation 509) so that the IPv4/IPv6 user node 111 communicates with the IPv6 usednode 131 using IPv6 (Operation 510). - FIG. 6 is a flowchart describing a method of establishing a bi-directional tunnel according to another embodiment of the present invention.
Operations 601 to 604 of FIG. 6 are the same asOperations 501 to 504 of FIG. 5, and Operations 608 to 613 of FIG. 6 are the same as Operations 504 to 510 of FIG. 5, and therefore these operations will not be described again. - Referring to FIG. 6, since the
TEP 121 fails to establish the unidirectional tunnel from theTEP 121 to the IPv4/IPv6 user node 111, another TEP is used to establish the unidirectional tunnel. A first TEP corresponding to theTEP 121 of FIG. 5 and a second TEP corresponding to another TEP are shown in FIG. 6. - The IPv4/
IPv6 user node 111 requests the first TEP to establish the unidirectional tunnel. However, since the fist TEP fails to establish the unidirectional tunnel (Operation 605), it sends a tunnel configuration response message that indicates failure in establishing the unidirectional tunnel to the IPv4/IPv6 user node 111 (Operation 606). There are several reasons that the fist TEP can fail to establish the unidirectional tunnel. The reasons are described in code information defined in a message region with reference to FIG. 2. - The IPv4/
IPv6 user node 111 receives the tunnel configuration response message that indicates failure in establishing the unidirectional tunnel from the first TEP and informs a user of the tunnel configuration failure (Operation 607). The IPv4/IPv6 user node 111 sends a tunnel configuration request message using an IPv4 address of a TEP other than the first TEP of those received from the DHCP server 112 (Operation 608). If the IPv4 address is the IPv4 address of the second TEP, the IPv4/IPv6 user node 111 can send the tunnel configuration request message to the second TEP. If there is no IPv4 address except that of the first TEP, the IPv4/IPv6 user node 111 sends the tunnel configuration request message to the first TEP again. The second TEP establishes the unidirectional tunnel as described in theTEP 121 of FIG. 5 (Operation 609). - As described above, the bi-directional tunnel between a user node and a TEP is automatically established without user assistance, so that the tunneling service is continuously provided to the user node in spite of changes in a network connected to the user node. For example, the user node in a mobile IPv4 network environment can be continuously connected to an IPv6 network according to the method of establishing the bidirectional tunnel.
- The user is not required to know TEP information of a new network, and a TEP manager is not required to know information of changed user nodes.
- While this invention has been particularly shown and described with reference to preferred embodiments thereof, it will be understood by those skilled 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 appended claims.
- Although a few preferred embodiments have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims.
Claims (16)
- A method for establishing a bi-directional tunnel (125) between a user node (111) and a first tunnel end point TEP (121) of one or more TEPs in a first network (100) including the user node (111), a dynamic host configuration protocol DHCP server (112), and the one or more TEPs (121), the method comprising:operating the user node (111) in order to establish the bi-directional tunnel (125), wherein operating the user node (111) comprises:requesting network information necessary to establish the bi-directional tunnel (125) from the DHCP server (112);establishing a unidirectional tunnel from the user node (111) to the first TEP (121) of one or more TEPs based on the received network information when the user node (111) receives the network information from the DHCP server (112);requesting one of the one or more TEPs to establish a unidirectional tunnel from said one TEP of the one or more TEPs to the user node (111); andestablishing an address of the user node (111) in a second network when the user node (111) receives a router advertisement RA message of a second network (130) with which the user node (111) wishes to communicate from the first TEP (121) of one or more TEPs required to establish the unidirectional tunnel.
- The method of claim 1, wherein the network information comprises an address on the first network (100) of the first TEP (121) of one or more TEPs.
- The method of claim 2, wherein the network information further comprises the address of the user node (111) in the first network (100).
- The method of any preceding claim, wherein operating the user node (111) further comprises: informing a user of failure to establish the bi-directional tunnel (125) when the user node (111) receives a tunnel configuration failure message from the first TEP (121) of one or more TEPs.
- The method of any preceding claim, wherein operating the user node (111) further comprises: requesting another TEP of the one or more TEPs to establish the unidirectional tunnel using the address on the first network (100) of another TEP of the one or more TEPs received from the DHPC server when the user node (111) receives the tunnel configuration failure message from the first TEP (121) of the one or more TEPs.
- The method of any preceding claim, wherein the user node (111) generates the address of the second network (130) based on a prefix of the RA message of the second network (130).
- The method of any preceding claim, wherein the first network (100) is an IPv4 network, and the second network (130) is an IPv6 network.
- A method of establishing a bi-directional tunnel (125) between a user node (111) and a first TEP (121) of one or more TEPs in a first network (100) including the user node (111), a DHCP server (112), and the one or more TEPs, the method comprising:operating the first TEP (121) of one or more TEPs in order to establish the bi-directional tunnel (125), wherein operating the first TEP (121) of one or more TEPs comprises:establishing a unidirectional tunnel from the first TEP (121) of one or more TEPs to the user node (111) based on information network included in the tunnel configuration request message when the first TEP (121) of one or more TEPs receives a tunnel configuration request message from the user node (111); andsending the RA message of a second network (130) with which the user node (111) wishes to communicate to the user node (111) when the first TEP (121) of one or more TEPs establishes the unidirectional tunnel.
- The method of claim 8 further comprising: sending a message informing of the configuration failure of the unidirectional tunnel to the user node (111) when the first TEP (121) of one or more TEPs fails to establish the unidirectional tunnel.
- The method of claim 9, wherein the message informing of the failure to establish the unidirectional tunnel is configured using code information regarding a plurality of predetermined failure reasons.
- The method of any one of claims 8 to 10, wherein the first network (100) is an IPv4 network, and the second network (130) is an IPv6 network.
- The method of any one of claims 8 to 11, wherein the tunnel configuration request message is sent by using any one of TCP Transport Control Protocol, UDP User Datagram Protocol, and ICMP Internet Control Message Protocol.
- A user node adapted to be used in a system for establishing a bi-directional tunnel (125) between a user node (111) and a first TEP (121) of one or more TEPs in a first network (100) including the user node (111), a DHCP server (112), and the one or more TEPs; wherein the user node (111) comprises:a tunnel configuration agent (300) for receiving network information necessary to establish the bi-directional tunnel (125) from the DHCP server (112), for establishing a unidirectional tunnel from the user node (111) to the first TEP (121) of one or more TEPs based on the received network information, and for communicating in order to establish the bi-directional tunnel (125) with the first TEP (121) of one or more TEPs;an address configuration unit (320) for establishing an address of the second network (130) of the user node (111) based on the RA message when the RA message of a second network (130) with which the user node (111) wishes to communicate is provided from the first TEP (121) of one or more TEPS; anda dual stack (330) for managing an address of the first network (100) and the address of the second network (130) of the user node (111).
- The user node of claim 13, wherein the tunnel configuration agent (300) comprises:a receiver (301) for receiving the network information:a controller (302) for controlling to establish the bi-directional tunnel (125);a tunnel information handler (303) operable to be controlled by the controller (302) and for managing tunnel information to establish the unidirectional tunnel in the network information;a tunnel configuration unit (304) for establishing the unidirectional tunnel based on the tunnel information provided from the tunnel information handler (303);a message creator & transmitter (305) operable to be controlled by the controller (302) and for creating a message to be provided to the first TEP (121) of one or more TEPs in order to establish the bi-directional tunnel (125), and for providing the controller (302) with the message provided from the first TEP (121) of one or more TEPs; anda client (306) transmitting the message provided from the message creator & transmitter (305) to the first TEP of one or more TEPs (121), and providing the message creator & transmitter (305) with the message received from the first TEP (121) of one or more TEPs.
- A system for establishing a bi-directional tunnel (125) between a user node (111) and a first TEP (121) of one or more TEPs in a first network (100) including the user node (111), a DHCP server (112), and the one or more TEPs, wherein the first TEP (121) of one or more TEPs comprises:a port (314) for exchanging messages with the user node (111) in order to establish the bi-directional tunnel (125) ;a parser (312) for parsing messages received through the port (314);a controller (302) for controlling to establish the unidirectional tunnel from the first TEP (121) to the user node (111) based on the message parsed by the parser (312);a tunnel information handler (303) operable to be controlled by the controller (302) and for managing network information necessary to establish the unidirectional tunnel; anda tunnel configuration unit (304) for establishing the unidirectional tunnel based on tunnel information provided from the tunnel information handler (303).
- The system of claim 15, wherein the first TEP (121) of one or more TEPs further comprises:a communication processing unit (350) for sending the RA message of a second network (130) to the user node (111) communicate when the unidirectional tunnel is established.
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020040086547A KR100636186B1 (en) | 2004-10-28 | 2004-10-28 | Bidirectional tunnel establishment method and system thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1653704A1 EP1653704A1 (en) | 2006-05-03 |
EP1653704B1 true EP1653704B1 (en) | 2007-11-07 |
Family
ID=35613996
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP05256641A Ceased EP1653704B1 (en) | 2004-10-28 | 2005-10-26 | Method and system for establishing a bidirectional tunnel |
Country Status (5)
Country | Link |
---|---|
US (1) | US8130671B2 (en) |
EP (1) | EP1653704B1 (en) |
KR (1) | KR100636186B1 (en) |
CN (1) | CN100477619C (en) |
DE (1) | DE602005003189T2 (en) |
Families Citing this family (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100803590B1 (en) * | 2003-10-31 | 2008-02-19 | 삼성전자주식회사 | System for providing tunnel service capable of data communication between different type of networks |
KR100705570B1 (en) * | 2005-03-09 | 2007-04-10 | 삼성전자주식회사 | AUTOMATIC CONFIGURED TUNNELING SYSTEM AND METHOD BETWEEN IPv4 NETWORK AND IPv6 NETWORK |
US8559369B2 (en) | 2006-02-22 | 2013-10-15 | Elad Barkan | Wireless internet system and method |
TW200744396A (en) * | 2006-05-26 | 2007-12-01 | Hon Hai Prec Ind Co Ltd | Mobile node and roaming method therefor, home agent and packet processing method therefor, and network communication system |
KR100901790B1 (en) * | 2006-12-04 | 2009-06-11 | 한국전자통신연구원 | CONTROL TUNNEL AND DIRECT TUNNEL CONFIGURATION METHOD IN IPv6 SERVICE PROVIDE SYSTEM BASED IPv4 NETWORK |
KR100862191B1 (en) | 2006-12-07 | 2008-10-09 | 한국전자통신연구원 | Automatic tunnel configuration method using router advertisement message |
CN101540995B (en) * | 2008-03-21 | 2011-06-08 | 华为技术有限公司 | Method for acquiring information, user equipment and network side equipment |
CN101577657B (en) | 2008-05-08 | 2012-05-23 | 华为技术有限公司 | Method of tunnel establishment and system for realizing tunnel establishment |
WO2010004363A1 (en) * | 2008-07-07 | 2010-01-14 | Nokia Corporation | Methods, apparatuses, and computer program products for facilitating transition between network address protocols |
CN101394361B (en) * | 2008-11-10 | 2011-07-27 | 杭州华三通信技术有限公司 | Packet transmission method, device and system |
KR101057815B1 (en) | 2008-12-04 | 2011-08-19 | 한국전자통신연구원 | Tunneling-based mobility support device and method |
US20100235515A1 (en) * | 2009-03-16 | 2010-09-16 | Posco Ict Company Ltd. | Method and apparatus for managing connection |
US8719337B1 (en) * | 2009-04-27 | 2014-05-06 | Junaid Islam | IPv6 to web architecture |
CN101599859B (en) * | 2009-06-30 | 2011-07-20 | 华为技术有限公司 | Method, system and nodes for protecting two-way tunnel |
CN102209121A (en) * | 2010-03-29 | 2011-10-05 | 杭州华三通信技术有限公司 | Method and device for intercommunication between Internet protocol version 6 (IPv6) network and Internet protocol version 4 (IPv4) network |
US8341276B1 (en) * | 2010-07-23 | 2012-12-25 | Sprint Communications Company L.P. | Negotiating internet protocol addresses in a network |
US8848702B2 (en) * | 2011-02-19 | 2014-09-30 | Cisco Technology, Inc. | Automated transitioning between different communication protocols in a network |
US8817815B2 (en) * | 2011-12-22 | 2014-08-26 | Cisco Technology, Inc. | Traffic optimization over network link |
US10070369B2 (en) | 2013-01-02 | 2018-09-04 | Comcast Cable Communications, Llc | Network provisioning |
US9191318B1 (en) | 2013-04-29 | 2015-11-17 | Cisco Technology, Inc. | Transitioning between communication protocols between networks |
US10021027B2 (en) | 2013-04-30 | 2018-07-10 | Comcast Cable Communications, Llc | Network validation with dynamic tunneling |
US9967906B2 (en) | 2015-01-07 | 2018-05-08 | Cisco Technology, Inc. | Wireless roaming using a distributed store |
US9985837B2 (en) | 2015-07-23 | 2018-05-29 | Cisco Technology, Inc. | Refresh of the binding tables between data-link-layer and network-layer addresses on mobility in a data center environment |
US10326204B2 (en) | 2016-09-07 | 2019-06-18 | Cisco Technology, Inc. | Switchable, oscillating near-field and far-field antenna |
CN106656802B (en) * | 2016-12-21 | 2019-06-21 | 北京格林伟迪科技股份有限公司 | A kind of end-to-end tunnel generation method |
US10440723B2 (en) | 2017-05-17 | 2019-10-08 | Cisco Technology, Inc. | Hierarchical channel assignment in wireless networks |
US10555341B2 (en) | 2017-07-11 | 2020-02-04 | Cisco Technology, Inc. | Wireless contention reduction |
US10440031B2 (en) | 2017-07-21 | 2019-10-08 | Cisco Technology, Inc. | Wireless network steering |
US10735981B2 (en) | 2017-10-10 | 2020-08-04 | Cisco Technology, Inc. | System and method for providing a layer 2 fast re-switch for a wireless controller |
US10375667B2 (en) | 2017-12-07 | 2019-08-06 | Cisco Technology, Inc. | Enhancing indoor positioning using RF multilateration and optical sensing |
US11277280B2 (en) * | 2018-03-19 | 2022-03-15 | Cable Television Laboratories, Inc. | Content centric networking systems and methods |
US10505718B1 (en) | 2018-06-08 | 2019-12-10 | Cisco Technology, Inc. | Systems, devices, and techniques for registering user equipment (UE) in wireless networks using a native blockchain platform |
US10673618B2 (en) | 2018-06-08 | 2020-06-02 | Cisco Technology, Inc. | Provisioning network resources in a wireless network using a native blockchain platform |
US11936629B2 (en) | 2018-06-21 | 2024-03-19 | VMware LLC | System and method for creating a secure hybrid overlay network |
EP3811590A4 (en) * | 2018-06-21 | 2022-06-15 | 8E14 Networks, Inc | System and method for creating a secure hybrid overlay network |
US10873636B2 (en) | 2018-07-09 | 2020-12-22 | Cisco Technology, Inc. | Session management in a forwarding plane |
US10671462B2 (en) | 2018-07-24 | 2020-06-02 | Cisco Technology, Inc. | System and method for message management across a network |
US11252040B2 (en) | 2018-07-31 | 2022-02-15 | Cisco Technology, Inc. | Advanced network tracing in the data plane |
US10735209B2 (en) | 2018-08-08 | 2020-08-04 | Cisco Technology, Inc. | Bitrate utilization feedback and control in 5G-NSA networks |
US10623949B2 (en) | 2018-08-08 | 2020-04-14 | Cisco Technology, Inc. | Network-initiated recovery from a text message delivery failure |
US10284429B1 (en) | 2018-08-08 | 2019-05-07 | Cisco Technology, Inc. | System and method for sharing subscriber resources in a network environment |
US10949557B2 (en) | 2018-08-20 | 2021-03-16 | Cisco Technology, Inc. | Blockchain-based auditing, instantiation and maintenance of 5G network slices |
US10374749B1 (en) | 2018-08-22 | 2019-08-06 | Cisco Technology, Inc. | Proactive interference avoidance for access points |
US10567293B1 (en) | 2018-08-23 | 2020-02-18 | Cisco Technology, Inc. | Mechanism to coordinate end to end quality of service between network nodes and service provider core |
US10230605B1 (en) | 2018-09-04 | 2019-03-12 | Cisco Technology, Inc. | Scalable distributed end-to-end performance delay measurement for segment routing policies |
US10652152B2 (en) | 2018-09-04 | 2020-05-12 | Cisco Technology, Inc. | Mobile core dynamic tunnel end-point processing |
US10779188B2 (en) | 2018-09-06 | 2020-09-15 | Cisco Technology, Inc. | Uplink bandwidth estimation over broadband cellular networks |
US11558288B2 (en) | 2018-09-21 | 2023-01-17 | Cisco Technology, Inc. | Scalable and programmable mechanism for targeted in-situ OAM implementation in segment routing networks |
US10285155B1 (en) | 2018-09-24 | 2019-05-07 | Cisco Technology, Inc. | Providing user equipment location information indication on user plane |
US10601724B1 (en) | 2018-11-01 | 2020-03-24 | Cisco Technology, Inc. | Scalable network slice based queuing using segment routing flexible algorithm |
US11570207B2 (en) * | 2019-12-31 | 2023-01-31 | Juniper Networks, Inc. | Dynamic security actions for network tunnels against spoofing |
US20230379248A1 (en) * | 2020-09-22 | 2023-11-23 | Google Llc | Adapting IPv4-only Devices for IPv6 Communication |
EP3993352A1 (en) * | 2020-10-29 | 2022-05-04 | Juniper Networks, Inc. | Supporting dynamic host configuration protocol-based customer premises equipment in fifth generation wireline and wireless convergence |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8516055B2 (en) * | 1998-05-29 | 2013-08-20 | Research In Motion Limited | System and method for pushing information from a host system to a mobile data communication device in a wireless data network |
US6286038B1 (en) * | 1998-08-03 | 2001-09-04 | Nortel Networks Limited | Method and apparatus for remotely configuring a network device |
US6708219B1 (en) | 1999-10-26 | 2004-03-16 | 3Com Corporation | Method and system for dual-network address utilization |
US20010040895A1 (en) * | 2000-03-16 | 2001-11-15 | Templin Fred Lambert | An IPv6-IPv4 compatibility aggregatable global unicast address format for incremental deployment of IPv6 nodes within IPv4 |
JP3823674B2 (en) | 2000-03-27 | 2006-09-20 | 株式会社日立製作所 | COMMUNICATION METHOD AND COMMUNICATION CONTROL DEVICE WITH PROTOCOL CONVERSION |
US6862274B1 (en) * | 2000-10-26 | 2005-03-01 | Industrial Technology Research Institute | Method and system capable of providing mobility support for IPv4/IPv6 inter-networking |
US8046452B2 (en) * | 2001-03-08 | 2011-10-25 | British Telecommunications Public Limited Company | Inter-network address translator that is separately addressable from address alias assignment process |
JP3744391B2 (en) | 2001-08-09 | 2006-02-08 | 株式会社日立製作所 | IPv4-IPv6 translation device, DNS proxy device, and IP address notification method |
EP1421810B1 (en) * | 2001-08-29 | 2007-10-31 | Research In Motion Limited | System and method for addressing a mobile device in an ip-based wireless network |
KR100423500B1 (en) | 2002-01-29 | 2004-03-18 | 삼성전자주식회사 | Converting Apparatus for converting internet protocol address and Home network system using thereof |
WO2003090488A1 (en) * | 2002-04-15 | 2003-10-30 | Flarion Technologies, Inc. | Methods and apparatus for the utilization of multiple uplinks in reverse tunneling |
AU2003223604A1 (en) * | 2002-04-15 | 2003-11-03 | Flarion Technologies, Inc. | Tunneling between different addressing domains |
US7461251B2 (en) * | 2002-05-09 | 2008-12-02 | Canon Kabushiki Kaisha | Public key certification issuing apparatus |
KR100496637B1 (en) | 2002-06-07 | 2005-06-28 | (주)아이엠넷피아 | A Method of IPv4 communication in IPv6 Wireless LAN |
US20040006641A1 (en) * | 2002-07-02 | 2004-01-08 | Nischal Abrol | Use of multi-format encapsulated internet protocol messages in a wireless telephony network |
CA2393547A1 (en) * | 2002-07-15 | 2004-01-15 | Hexago Inc. | Method and apparatus for connecting ipv6 devices through an ipv4 network using a tunneling protocol |
JP4034611B2 (en) | 2002-07-18 | 2008-01-16 | 東日本電信電話株式会社 | Network system and network branching device |
JP4056849B2 (en) * | 2002-08-09 | 2008-03-05 | 富士通株式会社 | Virtual closed network system |
JP2004104664A (en) | 2002-09-12 | 2004-04-02 | Telecommunication Advancement Organization Of Japan | Network connection device |
JP4063024B2 (en) * | 2002-09-13 | 2008-03-19 | 三菱電機株式会社 | Mobility management method using distributed MobileIP |
US20040088385A1 (en) * | 2002-11-01 | 2004-05-06 | Hexago Inc. | Method and apparatus for connecting IPV4 devices through an IPV6 network using a tunnel setup protocol |
DE60335741D1 (en) * | 2002-11-29 | 2011-02-24 | Freebit Co Ltd | SERVER FOR ROUTING CONNECTION TO A CLIENT DEVICE |
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 |
KR100560737B1 (en) | 2003-02-18 | 2006-03-13 | 삼성전자주식회사 | appatus for converting IPv4-to-IPv6 using dual stack and method thereof |
KR20040082655A (en) * | 2003-03-19 | 2004-09-30 | 삼성전자주식회사 | Mobile ip communication system by use of dual stack transition mechanism and method thereof |
CN1529480B (en) | 2003-10-08 | 2010-04-14 | 中国科学院计算技术研究所 | IP network protocol conversion method |
US7505460B2 (en) * | 2004-04-26 | 2009-03-17 | Intel Corporation | Address validating data structure used for validating addresses |
US7548523B2 (en) * | 2004-06-30 | 2009-06-16 | Qualcomm Incorporated | Dynamic configuration of IP for a terminal equipment attached to a wireless device |
-
2004
- 2004-10-28 KR KR1020040086547A patent/KR100636186B1/en not_active IP Right Cessation
-
2005
- 2005-10-26 EP EP05256641A patent/EP1653704B1/en not_active Ceased
- 2005-10-26 DE DE602005003189T patent/DE602005003189T2/en active Active
- 2005-10-27 US US11/259,275 patent/US8130671B2/en not_active Expired - Fee Related
- 2005-10-28 CN CNB2005101170123A patent/CN100477619C/en not_active Expired - Fee Related
Also Published As
Publication number | Publication date |
---|---|
US8130671B2 (en) | 2012-03-06 |
KR20060037556A (en) | 2006-05-03 |
DE602005003189D1 (en) | 2007-12-20 |
CN1770718A (en) | 2006-05-10 |
KR100636186B1 (en) | 2006-10-19 |
CN100477619C (en) | 2009-04-08 |
US20060092964A1 (en) | 2006-05-04 |
DE602005003189T2 (en) | 2008-08-28 |
EP1653704A1 (en) | 2006-05-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1653704B1 (en) | Method and system for establishing a bidirectional tunnel | |
EP1697852B1 (en) | Providing location-specific services to a mobile node | |
US20050175020A1 (en) | Tunneling service method and system | |
US7644171B2 (en) | Mobile networking system and method using IPv4 and IPv6 | |
CN101207604B (en) | Virtual machine system and communication processing method thereof | |
US20060069836A1 (en) | Communication system and method for upgrade of user terminal software and user terminal upgraded by the same | |
KR20020082483A (en) | Address acquisition | |
EP2082329B1 (en) | System and method for redirecting requests | |
US8477664B2 (en) | Communication platform and method for packet communication between a service provider and a radio communication device | |
EP2434716A1 (en) | Method and system for acquiring host identity tag | |
JP5638063B2 (en) | COMMUNICATION DEVICE, COMMUNICATION DEVICE CONTROL METHOD, PROGRAM | |
US20040117473A1 (en) | Proxy network control apparatus | |
WO2009005212A1 (en) | Ipv6 over ipv4 transition method and apparatus for improving performance of control server | |
EP1990953B1 (en) | A method and device for determining home agent attached by mobile node | |
CN100393039C (en) | Network administration method for no-IP address device | |
EP1495595B1 (en) | A system, an arrangement and a method relating to ip-addressing | |
EP2124397A1 (en) | A method for transfering the ip transmission session and the equipment whereto | |
JP2006262352A (en) | Mobile terminal, packet relay device, communication system, and communication method | |
JP2004007073A (en) | Method for handover in radio communication and radio communication apparatus | |
KR100877850B1 (en) | Method for reducing the overload of a home agent in the Mobile Internet Protocol Network | |
KR20050061959A (en) | System for serving data |
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: 20051108 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL BA HR MK YU |
|
17Q | First examination report despatched |
Effective date: 20060608 |
|
AKX | Designation fees paid |
Designated state(s): DE FR GB IT NL |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
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 IT NL |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 602005003189 Country of ref document: DE Date of ref document: 20071220 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: 20080808 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 12 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 13 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: FR Payment date: 20180927 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: NL Payment date: 20180921 Year of fee payment: 14 Ref country code: GB Payment date: 20180921 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20180920 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: IT Payment date: 20181011 Year of fee payment: 14 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602005003189 Country of ref document: DE |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: MM Effective date: 20191101 |
|
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: 20200501 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191101 |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20191026 |
|
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: 20191031 Ref country code: IT Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191026 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20191026 |