# US 2008/0304482 A1 · Device and method for communicating with a legacy device, network or application

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0304482 A1
- Document ID: US20080304482A1
- Status: Published application
- Kind: A1
- Application number: 12/155,740
- Filed: 2008-06-09
- Published: 2008-12-11
- Earliest claimed: 2007-06-07
- Assignees: Ambriel Technologies
- Inventors: Stephen J. Grassi; Samuel A. Moats; Oscar F. Roeder; Faith B. Power
- Web page: https://patentgrep.com/patent/US20080304482A1

## CPC

- H04L 61/251: between different IP versions
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L 69/167: Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6 (translation of Internet protocol [IP] addresses H04L61/2503)
- H04L 61/4511: using domain name system [DNS]
- H04L 2101/659: Internet protocol version 6 [IPv6] addresses
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A translation device allows communication between two entities that are not compatible. The two entities can include a legacy entity that uses an address format not compatible with a newer entity. The translation device receives a packet for the legacy entity and converts its address to one that is compatible with the legacy entity. The translation device may use different processes to convert the address in accordance with messaging protocols, packet configuration or the destination address desired. Once the packet includes a compatible address, the device sends the packet to the legacy entity.

## Claims

### Claim 1

A method for communicating with an entity, the method comprising:
receiving a packet having an address not compatible with the entity;
converting the address to a compatible address; and
sending the packet to the entity according to the compatible address.

### Claim 2 (depends on 1)

The method of claim 1, wherein the converting step includes translating the address according to a protocol.

### Claim 3 (depends on 1)

The method of claim 1, wherein the converting step includes adding a prefix to the address.

### Claim 4 (depends on 1)

The method of claim 1, wherein the converting step includes converting the address to a set value for the compatible address.

### Claim 5 (depends on 1)

The method of claim 1, wherein the entity includes a device, network or application.

### Claim 6 (depends on 1)

The method of claim 1, wherein the entity includes a legacy entity.

### Claim 7 (depends on 6)

The method of claim 6, wherein the converting step includes retrieving the compatible address from a table.

### Claim 8

A translation device comprising:
a first port to exchange a packet with a first entity;
a second port to exchange the packet with a second entity; and
a translator to convert the packet to include an address compatible with the second entity.

### Claim 9 (depends on 8)

The translation device of claim 8, further comprising at least one table accessible by the translator to provide the compatible address.

### Claim 10 (depends on 8)

The translation device of claim 8, further comprising at least one table accessible by the translator to store data indicating the packet was received at the first port.

### Claim 11 (depends on 8)

The translation device of claim 8, wherein said translator converts the packet by translating an incompatible address of the packet to the compatible address.

### Claim 12 (depends on 8)

The translation device of claim 8, wherein the compatible address includes a prefix.

### Claim 13 (depends on 11)

The translation device of claim 11, wherein the incompatible address is converted to the compatible address using a formula.

### Claim 14

A method for communicating with an entity, the method comprising:
determining an address of a packet destined for the entity is not compatible;
determining a format for the packet;
selecting a conversion process for the address according to the format;
converting the address of the packet to a compatible address using the conversion process; and
sending the packet to the entity using the compatible address.

### Claim 15 (depends on 14)

The method of claim 14, wherein the converting step includes adding a prefix to the address.

### Claim 16 (depends on 14)

The method of claim 14, wherein the converting step includes translating the address to the compatible address using a formula.

### Claim 17 (depends on 14)

The method of claim 14, wherein the converting step includes converting the address to the compatible address using a value from a table.

### Claim 18 (depends on 14)

The method of claim 14, further comprising determining a protocol corresponding to the format of the packet.

### Claim 19 (depends on 18)

The method of claim 18, wherein the selecting step includes selecting the conversion process compatible with the protocol.

### Claim 20 (depends on 14)

The method of claim 14, wherein the packet includes an outer layer and an inner layer, such that the conversion process is selected according to the format of the outer layer.

### Claim 21 (depends on 14)

The method of claim 14, wherein the entity includes a legacy device.
