IP Library Granted Patent US 9,413,694
Granted Patent B2
US 9,413,694 · App. 14/835,517 · Granted Aug 9, 2016

Method for performing protocol translation in a network switch

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,413,694
App. No.
14/835,517
Granted
Aug 9, 2016
Kind
B2
Abstract

A system and method are disclosed for processing a packet. Processing the packet comprises receiving the packet; translating the packet from a first protocol-specific format to a canonical packet format; translating the packet from the canonical packet format to a second protocol-specific format; and forwarding the packet.

Claims (31)

1. A method, comprising:

converting, by a network device comprising at least one processor, a packet from a protocol-specific format, of a set of protocol-specific formats supported by a network device, to a canonical packet format yielding a canonical packet that is not protocol-specific; and

forwarding, by the network device, the canonical packet to an egress processing engine of the network device,

wherein the canonical packet format comprises at least a multiple protocol-specific field representing a first field that is common to multiple protocol-specific formats of the set and a protocol-specific field representing a second field that is specific exclusively to one protocol-specific format of the set.

2. The method of claim 1 , wherein the converting comprises configuring the canonical packet to be translatable to any of the set of protocol-specific formats.

3. The method of claim 1 , further comprising receiving, by the network device, the packet via an ingress link interface of the network device.

4. The method of claim 1 , wherein the converting comprises converting by a pooling switch device.

5. The method of claim 1 , wherein the canonical packet format further comprises a shared field configured to contain at least a first value associated with a third field of a first protocol-specific format of the set and a second value associated with a fourth field of a second protocol-specific format of the set, and wherein the third field is different than the fourth field.

6. The method of claim 5 , wherein the converting comprises copying information associated with another protocol-specific field of the packet to the shared field of the canonical packet.

7. The method of claim 1 , wherein the set of protocol-specific formats comprises at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.

8. The method of claim 1 , wherein the converting comprises:

in response to determining that the protocol-specific format is one of the multiple protocol-specific formats, copying first information from the first field of the packet to the multiple protocol-specific field of the canonical packet; and

in response to determining that the protocol-specific format is the one protocol-specific format, copying second information from the second field of the packet to the protocol-specific field of the canonical packet.

9. The method of claim 1 , further comprising:

converting, by the network device, the canonical packet from the canonical packet format to another protocol-specific format of the set yielding a converted packet; and

forwarding, by the network device, the converted packet to an egress link interface of the network device.

10. A device, comprising:

an ingress processing engine configured to convert a packet from a protocol-specific format, of multiple protocol-specific formats supported by the device, to a generic packet format to yield a generic packet that is not protocol-specific, and to forward the generic packet to an egress processing engine of the device,

wherein the generic packet format comprises at least a multiple protocol-specific field corresponding to a first field that is common to more than one of the multiple protocol-specific formats, and a protocol-specific field corresponding to a second field that is specific to only one of the multiple protocol-specific formats.

11. The device of claim 10 , further comprising an ingress interface configured to receive the packet in the protocol-specific format.

12. The device of claim 10 , wherein the generic packet format is configured to be translated from the generic packet format to any of the multiple protocol-specific formats.

13. The device of claim 10 , wherein the device comprises a pooling switch device.

14. The device of claim 10 , wherein the generic packet format further comprises a shared field configured to contain at least a first value associated with a third field of a first of the multiple protocol-specific formats and a second value associated with a fourth field of a second of the multiple protocol-specific formats, and wherein the third field is different than the fourth field.

15. The device of claim 14 , wherein the ingress processing engine is configured to copy information associated with another protocol-specific field of the packet in the protocol-specific format to the shared field of the generic packet.

16. The device of claim 10 , wherein the multiple protocol-specific formats comprises at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.

17. The device of claim 10 , further comprising an egress processing engine configured to convert the generic packet from the generic packet format to one of the multiple protocol-specific formats to yield a converted packet, and to output the converted packet via an egress link interface.

18. A non-transitory computer-readable medium having stored thereon instructions that, in response to execution, cause a device to perform operations, comprising:

translating a packet from a protocol-specific format, of a set of protocol-specific formats supported by the device, to a canonical packet format to yield a canonical packet that is not protocol-specific,

wherein the canonical packet format comprises at least a multiple protocol-specific field corresponding to a first field that is common to multiple protocol-specific formats of the set and a protocol-specific field corresponding to a second field that is specific exclusively to one protocol-specific format of the set.

19. The non-transitory computer-readable medium of claim 18 , wherein the canonical packet is configured to be translated to any of the set of protocol-specific formats.

20. The non-transitory computer-readable medium of claim 18 , wherein the set of protocol-specific formats comprises at least one of an asynchronous transfer mode format, a frame relay format, an Ethernet format, or a multi-protocol label switching format.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 13, 2020
From: GLOBAL INNOVATION AGGREGATORS, LLC
To: K.MIZRA LLC
Reel/Frame 051579/0773 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2017
From: BRIXHAM SOLUTIONS LTD.
To: GLOBAL INNOVATION AGGREGATORS LLC.
Reel/Frame 043312/0218 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 25, 2015
From: HAMMERHEAD SYSTEMS, INC.
To: BRIXHAM SOLUTIONS LTD.
Reel/Frame 036418/0557 →