Kazuo D Hashimoto, 39209 Baywood Rd, Alameda, CA 94502

7746891, Jun 29, 2010

Apr 5, 2004

10/818662

Shu Yamamoto - Cupertino CA, US
Carl Williams - Palo Alto CA, US
Hidetoshi Yokota - Saitama, JP
Kazuo Hashimoto - Palo Alto CA, US

KDDI Corporation - Tokyo

H04L 12/28

370466, 370392, 370338

A mobile IPv6 dual-stack node engages in IPv6 communication while roaming within an IPv4-only network, for example using ISATAP. First, the node determines that it has moved Bnd obtains a new IPv4 address. After determining that the visited network contains no IPv6-enabled components, the node uses an IPv6 connect agent to engage in IPv6 communication. The node configures its care-of address using the IPv6 connect agent's routing information and the node's newly-obtained IPv4 address. In one embodiment, the node and the connect agent optimize the handoff when the nodes has moved but still uses the same connect agent. The node sends a binding updates to the connect agents comprising the node's old care-of address and the node's new care-of address. When the connect agent receives a packet destined for the node's previous care-of address, it forwards the packet to the node's currents care-of address, thereby reducing packet loss.

2004018, Sep 23, 2004

May 12, 2003

10/436679

Shu Yamamoto - Cupertino CA, US
Hidetoshi Yokota - Saitama-Shi, JP
Carl Williams - Palo Alto CA, US
Kazuo Hashimoto - Palo Alto CA, US

G06F015/16

709/200000

An Internet Service Provider provides IPv6 connectivity to a customer without requiring that the customer upgrade its network containing IPv4 components. The Internet Service Provider makes at least one point of presence including at least one IPv6 Connect Agent available to customers. The Internet Service Provider allows a customer's IPv6 enabled node located within the customer's network containing IPv4 components to automatically discover an IPv6 Connect Agent. The Internet Service Provider facilitates IPv6 communication between the customer's IPv6 enabled node and the discovered IPv6 Connect Agent, across the customer's network containing IPv4 components. The Internet Service Provider also facilitates IPv6 communication between the discovered IPv6 Connect Agent and an IPv6 entity located outside of the customer's network containing IPv4 components, thereby providing IPv6 communication between the customer's IPv6 enabled node and the IPv6 entity located outside of the customer's network containing IPv4 components.

2005001, Jan 20, 2005

Dec 4, 2003

10/729257

Hidetoshi Yokota - Saitama-Shi, JP
Shu Yamamoto - Cupertino CA, US
Carl Williams - Palo Alto CA, US
Kazuo Hashimoto - Palo Alto CA, US

G06F015/16

709227000

An IPv6 enabled node finds an IPv6 connect agent by using a Domain Name System (DNS) server. The IPv6 enabled node sends a query to the DNS server and, in response, receives one or more identifiers of one or more IPv6 connect agents. In one embodiment, an identifier comprises the name of an IPv6 connect agent. In this embodiment, the IPv6 enabled node then sends a name of a desired IPv6 connect agent to the DNS server and, in response, receives the address of that IPv6 connect agent. The IPv6 enabled node is then able to engage in IPv6 communication using that IPv6 connect agent. In another embodiment, an identifier comprises the address of an IPv6 connect agent. In this embodiment, the IPv6 enabled node is able to engage in IPv6 communication using that IPv6 connect agent without any further contact with the DNS server.

2005009, May 12, 2005

Sep 22, 2004

10/947880

Shu Yamamoto - Cupertino CA, US
Carl Williams - Palo Alto CA, US
Hidetoshi Yokota - Saitama-Shi, JP
Kazuo Hashimoto - Palo Alto CA, US

H04J003/24

370331000, 370352000, 370401000, 370466000, 370395540

A mobile dual-stack node engages in IPv6 communication while roaming within an IPv4-only network. The node determines that it has moved and obtains a new IPv4 address. After determining that the visited network contains no IPv6-enabled components, the node communicates with a tunnel broker to obtain a care-of address and a tunnel to an IPv6 connect agent (e.g., a tunnel server). If the obtained care-of address differs from the care-of address that the node had been using prior to the move, the node sends MIPv6 binding updates to its home agent and corresponding peers. The node can optimize the handoff when it has obtained a different care-of address by sending a binding update to the connect agent comprising the previous care-of address and the current care-of address. When the connect agent receives a packet destined for the previous care-of address, it forwards the packet to the current care-of address.