Zum Hauptinhalt springen

Enabling mobile IPv6 communication over a network containing IPv4 components using ISATAP

Yamamoto, Shu ; Williams, Carl ; et al.
2010
Online Patent

Titel:
Enabling mobile IPv6 communication over a network containing IPv4 components using ISATAP
Autor/in / Beteiligte Person: Yamamoto, Shu ; Williams, Carl ; Yokota, Hidetoshi ; Hashimoto, Kazuo
Link:
Veröffentlichung: 2010
Medientyp: Patent
Sonstiges:
  • Nachgewiesen in: USPTO Patent Grants
  • Sprachen: English
  • Patent Number: 7,746,891
  • Publication Date: June 29, 2010
  • Appl. No: 10/818662
  • Application Filed: April 05, 2004
  • Assignees: KDDI Corporation (Tokyo, JP)
  • Claim: 1. A method for a mobile dual-stack node to engage in IPv6 communication across a network containing IPv4 components, the method comprising: determining that the mobile dual-stack node has moved; obtaining a new IPv4 address of the mobile dual-stack node; determining that a visited network does not contain any IPv6-enabled components; determining an IPv4 address of an IPv6 connect agent, wherein determining the IPv4 address of the IPv6 connect agent comprises one of sending an IPv4 anycast message and contacting a Domain Name System server; obtaining a care-of address; and configuring the IPv6 connect agent with the care-of address.
  • Claim: 2. The method of claim 1 , wherein determining that the node has moved comprises: detecting that the node has detached from one of a first network and a first subnetwork; and detecting that the node has attached to one of a second network and a second subnetwork.
  • Claim: 3. The method of claim 1 , wherein obtaining a new IPv4 address comprises using one of Dynamic Host Control Protocol (DHCP) and Point-to-Point Protocol.
  • Claim: 4. The method of claim 1 , wherein determining that a visited network does not contain any IPv6-enabled components comprises not receiving, within a specified amount of time, an IPv6 router advertisement.
  • Claim: 5. The method of claim 1 , further comprising: responsive to determining that the determined IPv4 address of the IPv6 connect agent is identical to the IPv4 address of the IPv6 connect agent that the node had previously used, sending a binding update to the IPv6 connect agent.
  • Claim: 6. The method of claim 5 , wherein sending a binding update to the IPv6 connect agent comprises: sending a previous care-of address used by the node and the obtained care-of address.
  • Claim: 7. A method for an IPv6 connect agent to optimize handoffs when a client node has moved within an IPv4-only network, the method comprising: receiving a binding update responsive to a detection that the client node uses the same IPv6 connect agent for a previous IPv6 communication and a current IPv6 communication over the IPv4-only network, the binding update containing a first care-of address and a second care-of address, wherein the first care-of address is associated with the previous IPv6 communication over the IPv4-only network, and the second care-of address is associated with the current IPv 6 communication over the IPv4-only network; and responsive to receiving a packet sent to the first care-of address, sending the packet to the second care-of address.
  • Claim: 8. A system for a mobile dual-stack node to engage in IPv6 communication across a network containing IPv4 components, the system comprising: an IPv4 movement detection module configured to determine that the node has moved; an IPv4 dynamic address configuration module configured to obtain a new IPv4 address of the mobile dual-stack node; an IP layer type detection module configured to determine that a visited network does not contain any IPv6-enabled components; an IPv6 connect agent discovery module configured to determine an IPv4 address of an IPv6 connect agent, wherein the IPv6 connect agent discovery module is further configured to send an IPv4 anycast message or to contact a Domain Name System server; an ISATAP client module configured to obtain a care-of address; and an MIPv6 client module configured to configure the IPv6 connect agent with the care-of address.
  • Claim: 9. The system of claim 8 , wherein determining that the node has moved comprises: detecting that the node has detached from one of a first network and a first subnetwork; and detecting that the node has attached to one of a second network and a second subnetwork.
  • Claim: 10. The system of claim 8 , wherein obtaining a new IPv4 address comprises using one of Dynamic Host Control Protocol (DHCP) and Point-to-Point Protocol.
  • Claim: 11. The system of claim 8 , wherein determining that a visited network does not contain any IPv6-enabled components comprises not receiving, within a specified amount of time, an IPv6 router advertisement.
  • Claim: 12. The system of claim 8 , further comprising: a binding update module configured to send, responsive to determining that the determined IPv4 address of the IPv6 connect agent is identical to the IPv4 address of the IPv6 connect agent that the node had previously used, a binding update to the IPv6 connect agent.
  • Claim: 13. The system of claim 12 , wherein sending a binding update to the IPv6 connect agent comprises: sending a previous care-of address used by the node and the obtained care-of address.
  • Claim: 14. A system for an IPv 6 connect agent to optimize handoffs when a client node has moved within an IPv4-only network, the system comprising: a binding update module configured to receive a binding update responsive to a detection that the client node uses the same IPv6 connect agent for a previous IPv6 communication and a current IPv6 communication over the IPv4-only network, the binding update containing a first care-of address and a second care-of address, wherein the first care-of address is associated with the previous IPv6 communication over the IPv4-only network, and the second care-of address is associated with the current IPv6 communication over the IPv4-only network; and a packet forwarding module configured to send, responsive to receiving a packet sent to the first care-of address, the packet to the second care-of address.
  • Claim: 15. A computer readable medium containing a computer program product for a mobile dual-stack node to engage in IPv6 communication across a network containing IPv4 components, the computer program product making a computer execute the steps of: determining that the mobile dual-stack node has moved; obtaining a new IPv4 address of the mobile dual-stack node; determining that a visited network does not contain any IPv6-enabled components; determining an IPv4 address of an IPv6 connect agent including at least one of sending an IPv4 anycast message and contacting a Domain Name System server; obtaining a care-of address; and configuring the IPv6 connect agent with the care-of address.
  • Claim: 16. The computer readable medium of claim 15 , wherein determining that the node has moved comprises: detecting that the node has detached from one of a first network and a first subnetwork; and detecting that the node has attached to one of a second network and a second subnetwork.
  • Claim: 17. The computer readable medium of claim 15 , wherein obtaining a new IPv4 address comprises using one of Dynamic Host Control Protocol (DHCP) and Point-to-Point Protocol.
  • Claim: 18. The computer readable medium of claim 15 , wherein determining that a visited network does not contain any IPv6-enabled components comprises not receiving, within a specified amount of time, an IPv6 router advertisement.
  • Claim: 19. The computer readable medium of claim 15 , wherein the computer program product comprises making the computer further execute the step of: sending, responsive to determining that the determined IPv4 address of the IPv6 connect agent is identical to the IPv4 address of the IPv6 connect agent that the node had previously used, a binding update to the IPv6 connect agent.
  • Claim: 20. The computer readable medium of claim 19 , wherein sending a binding update to the IPv6 connect agent comprises: sending a previous care-of address used by the node and the obtained care-of address.
  • Claim: 21. A computer readable medium containing a computer program product for an IPv6 connect agent to optimize handoffs when a client node has moved within an IPv4-only network, the computer program product making a computer execute the steps of: receiving a binding update responsive to a detection that the client node uses the same IPv6 connect agent for a previous IPv6 communication and a current IPv6 communication over the IPv4-only network, the binding update containing a first care-of address and a second care-of address, wherein the first care-of address is associated with the previous IPv6 communication over the IPv4-only network, and the second care-of address is associated with the current IPv6 communication over the IPv4-only network; and sending, responsive to receiving a packet sent to the first care-of address, the packet to the second care-of address.
  • Claim: 22. A system for a mobile dual-stack node to engage in IPv6 communication across a network containing IPv4 components, the system comprising: means for determining that the node has moved; means for obtaining a new IPv4 address of the mobile dual-stack node; means for determining that a visited network does not contain any IPv6-enabled components; means for determining an IPv4 address of an IPv6 connect agent, wherein the means for determining the IPv4 address of an IPv6 connect agent comprises at least one of means for sending an IPv4 anycast message and means for contacting a Domain Name System server; means for obtaining a care-of address; and means for configuring the IPv6 connect agent with the care-of address.
  • Claim: 23. The system of claim 22 , wherein determining that the node has moved comprises: detecting that the node has detached from one of a first network and a first subnetwork; and detecting that the node has attached to one of a second network and a second subnetwork.
  • Claim: 24. The system of claim 22 , wherein obtaining a new IPv4 address comprises using one of Dynamic Host Control Protocol (DHCP) and Point-to-Point Protocol.
  • Claim: 25. The system of claim 22 , wherein determining that a visited network does not contain any IPv 6 -enabled components comprises not receiving, within a specified amount of time, an IPv6 router advertisement.
  • Claim: 26. The system of claim 22 , further comprising: means for sending, responsive to determining that the determined IPv4 address of the IPv6 connect agent is identical to the IPv4 address of the IPv6 connect agent that the node had previously used, a binding update to the IPv6 connect agent.
  • Claim: 27. The system of claim 26 , wherein sending a binding update to the IPv 6 connect agent comprises: sending a previous care-of address used by the node and the obtained care-of address.
  • Claim: 28. A system for an IPv6 connect agent to optimize handoffs when a client node has moved within an IPv4-only network, the system comprising: means for receiving a binding update responsive to a detection that the client node uses the same IPv6 connect agent for a previous IPv6 communication and a current IPv6 communication over the IPv4-only network, the binding update containing a first care-of address and a second care-of address, wherein the first care-of address is associated with the previous IPv6 communication over the IPv4-only network, and the second care-of address is associated with the current IPv6 communication over the IPv4-only network; and means for sending, responsive to receiving a packet sent to the first care-of address, the packet to the second care-of address.
  • Current U.S. Class: 370/466
  • Patent References Cited: 6172986 January 2001 Watanuki et al. ; 6553413 April 2003 Leighton et al. ; 6810411 October 2004 Coughlin et al. ; 6862274 March 2005 Tsao et al. ; 7191226 March 2007 Flykt et al. ; 7216154 May 2007 Chow et al. ; 7321598 January 2008 Blanchet et al. ; 2002/0012320 January 2002 Ogier et al. ; 2002/0150104 October 2002 Hamamoto et al. ; 2003/0074461 April 2003 Kang et al. ; 2004/0013130 January 2004 Blanchet et al. ; 2004/0136382 July 2004 Sundquist ; 2004/0137888 July 2004 Ohki ; 2004/0184422 September 2004 Shaheen ; 2004/0264465 December 2004 Dunk ; 2005/0160183 July 2005 Valli et al. ; 2008/0016233 January 2008 Schneider ; H10-313336 November 1998 ; H11-068850 March 1999 ; A-2001-268129 September 2001 ; A-2002-314618 October 2002 ; A-2003-018185 January 2003
  • Other References:
  • Primary Examiner: Jackson, Blane J
  • Attorney, Agent or Firm: Fenwick & West LLP

Klicken Sie ein Format an und speichern Sie dann die Daten oder geben Sie eine Empfänger-Adresse ein und lassen Sie sich per Email zusenden.

oder
oder

Wählen Sie das für Sie passende Zitationsformat und kopieren Sie es dann in die Zwischenablage, lassen es sich per Mail zusenden oder speichern es als PDF-Datei.

oder
oder

Bitte prüfen Sie, ob die Zitation formal korrekt ist, bevor Sie sie in einer Arbeit verwenden. Benutzen Sie gegebenenfalls den "Exportieren"-Dialog, wenn Sie ein Literaturverwaltungsprogramm verwenden und die Zitat-Angaben selbst formatieren wollen.

xs 0 - 576
sm 576 - 768
md 768 - 992
lg 992 - 1200
xl 1200 - 1366
xxl 1366 -