# US 2015/0146730 A1 · Heterogeneous media packet bridging

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

- Number: US 2015/0146730 A1
- Document ID: US20150146730A1
- Status: Published application
- Kind: A1
- Application number: 14/587,959
- Filed: 2014-12-31
- Published: 2015-05-28
- Earliest claimed: 2003-08-27
- Assignees: Fortinet, Inc.
- Applicants: Fortinet, Inc.
- Inventors: Sachin Desai; Rajesh Balay; Chandramouli Sargor
- Web page: https://patentgrep.com/patent/US20150146730A1

## CPC

- H04L 49/25: Routing or path finding in a switch fabric
- H04L 12/46: Interconnection of networks
- H04L 12/4625: {Single bridge functionality, e.g. connection of two networks over a single bridge}
- H04L 49/354: for supporting virtual local area networks [VLAN]
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Methods and systems for bridging network packets transmitted over heterogeneous media channels are provided. According to one embodiment, a network switching/routing blade server comprises network interfaces, including a first and second set operable to receive packets encapsulated within a first and second set of media transmissions, respectively, and each having a first and second framing media format, respectively. A single bridging domain is provided by a shared bridging application. A memory stores data structures for translating between the first and second framing media formats via an intermediate format. The netmods pass a received packet, through a switching fabric, to the bridging application, which determines a relay location for the packet and whether the relay location is among the other set of netmods. Responsive to an affirmative determination, the bridging application uses the translation data structures to translate the packet before relaying the packet to the relay location.

## Claims

### Claim 1

A network routing/switching blade server comprising:
a plurality of network interfaces, including a first set of network interfaces implemented within a first server blade and operable to receive network packets encapsulated within a first plurality of media transmissions each having a first framing media format of a plurality of framing media formats and a second set of network interfaces implemented within a second server blade and operable to transmit network packets encapsulated within a second plurality of media transmissions each having a second framing media format of the plurality of framing media formats, wherein the plurality of framing media formats include one or more of Asynchronous Transfer Mode (ATM), Gigabit Ethernet (GigE), Frame Relay (FR), Time-Division Multiplexing (TDM) and a wireless media format;
a plurality of processing resources implemented within one or more server blades coupled to the plurality of network interfaces and shared by the plurality of network interfaces, including a first processing resource upon which a virtual bridging application executes, the virtual bridging application representing a single bridging domain for all network packets received by the network routing/switching blade server;
a non-transitory memory, accessible to the first processing resource, having stored therein one or more translation data structures defining translations between the first framing media format and an intermediate format and between the intermediate format and the second framing media format;
a switching fabric server blade, coupled to the plurality of network interfaces, forwarding the network packets received from the first set of network interfaces to one or more of the plurality of processing resources;
wherein responsive to receiving a network packet, the first set of network interfaces pass the network packet to the virtual bridging application through the switching fabric server blade;
the virtual bridging application determines a relay location to which the network packet is to be relayed and whether the relay location is among the second set of network interfaces, which are associated with a disparate framing media format and a disparate media channel than that of the first set of network interfaces; and
responsive to an affirmative determination that the relay location is among the second set of network interfaces, the virtual bridging application uses the one or more translation data structures to translate the network packet to the second framing media format before relaying the network packet to the relay location.

### Claim 2 (depends on 1)

The network routing/switching blade server of claim 1, wherein the first set of network interfaces and the second set of network interfaces include at least one network interface in common.

### Claim 3 (depends on 1)

The network routing/switching blade server of claim 1, wherein the first set of network interfaces and the second set of network interfaces share no network interfaces in common.

### Claim 4 (depends on 1)

The network routing/switching blade server of claim 1, wherein the one or more translation data structures are dynamically configurable, thereby allowing the virtual bridging application to be dynamically configured to accommodate framing media translations desired to be performed by the network routing/switching blade server.

### Claim 5 (depends on 1)

The network routing/switching blade server of claim 1, wherein the virtual bridging application relays at least the network packet to one or more other applications running on a second processing resource of the plurality of processing resources in order to assist in bridging between a first media channel associated with a first network interface of the first set of network interfaces and a second media channel associated with a second network interface in the second set of network interfaces.

### Claim 6 (depends on 1)

The network routing/switching blade server of claim 1, wherein the virtual bridging application is dynamically instantiated, configured or modified using a graphical user interface application.

### Claim 7 (depends on 1)

The network routing/switching blade server of claim 1, wherein the virtual bridging application is provided as an Application Programming Interface (API) library.

### Claim 8 (depends on 7)

The network routing/switching blade server of claim 7, wherein the API is provided as one or more Dynamic Linked Libraries (DLLs).

### Claim 9 (depends on 7)

The network routing/switching blade of claim 7, wherein the API is provided as a shared library.

### Claim 10 (depends on 1)

The network routing/switching blade of claim 1, wherein the virtual bridging application is provided as an object-oriented class object having public and private methods.

### Claim 11 (depends on 1)

The network routing/switching blade of claim 1, wherein the network packet comprises an Ethernet frame and the virtual bridging application permits media agnostic Ethernet bridging between the first set of network interfaces and the second set of network interfaces.

### Claim 12 (depends on 1)

The network routing/switching blade of claim 1, wherein the one or more translation data structures include metadata associated with network packets encapsulated within a first plurality of media transmissions.

### Claim 13 (depends on 12)

The network routing/switching blade of claim 12, wherein the metadata includes Ethernet header data that is transmitted on top of network packets encapsulated within a first plurality of media transmissions.
