IP Library Granted Patent US 9,306,757
Granted Patent B2
US 9,306,757 · App. 13/850,681 · Granted Apr 5, 2016

Method and apparatus for distributing routing instructions over multiple interfaces of a data router

Inventors: Steven Clay Ellis (Los Gatos, CA); Deepak Kharbanda (San Jose, CA); Xiaoyan Chang (San Jose, CA)
Assignee: Pluris, Inc.
H04L12/18H04L12/185H04L12/4625H04L45/02H04L45/025H04L45/16H04L45/42H04L45/54H04L45/58H04L45/60H04L47/10H04L47/17H04L47/29H04L47/30H04L47/32
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,306,757
App. No.
13/850,681
Granted
Apr 5, 2016
Kind
B2
Abstract

A method for processing multicast data packets has steps for (a) requesting a second router upstream router by a multiple-processor data router to join a multicast group, the request including identification of a single physical ingress port from a plurality of available ports for receiving the multicast data packets; (b) preparing a multicast forwarding information base (MFIB) limited to only forwarding information incorporating the identified physical ingress port, and distributing the MFIB to a client software module hosting the identified physical ingress port; (c) receiving the multicast data packets at the identified ingress port; and (d) using only the MFIB to route the received multicast data packets.

Claims (22)

1. A method for processing multicast data packets comprising steps of:

(a) requesting a second upstream router by a multiple-processor data router to join a multicast group, the request including identification of a single physical ingress port from a plurality of available ports for receiving the multicast data packets;

(b) preparing a multicast forwarding information base (MFIB) limited to only forwarding information incorporating the identified physical ingress port, and distributing the MFIB to a client software module hosting the identified physical ingress port, causing data to be expected at the identified physical ingress port from the second upstream router;

(c) storing the MFIB locally at the client software module;

(d) receiving and identifying the multicast data packets at the identified ingress port as the expected data;

(e) accessing and using only the MFIB to route the received multicast data packets; and

(f) dropping packets received at the identified physical ingress port that are not identified as expected data.

2. The method of claim 1 wherein in step (b) the portion MFIB includes one or more of network layer address information, circuit ID metrics, and physical port metrics.

3. The method of claim 1 wherein in step (b) the MFIB follows protocol independent multicast (PIM).

4. The method of claim 3 wherein in step (b) distribution is from a PIM server to one or more PIM clients.

5. A multicast-enabled data router, comprising:

a plurality of processors including individual ones operating as clients managing multiple physical communication ports, and one processor functioning as a control processor having access to a multicast forwarding information base (MFIB); and

software executing on the processors, the software executing instructions implementing a process comprising:

(a) requesting a second upstream router by a multiple-processor data router to join a multicast group, the request including identification of a single physical ingress port from a plurality of available ports for receiving the multicast data packets;

(b) preparing a multicast forwarding information base (MFIB) limited to only forwarding information incorporating the identified physical ingress port, and distributing the MFIB to a client software module hosting the identified physical ingress port, causing data to be expected at the identified physical ingress port from the second upstream router;

(c) storing the MFIB locally at the client software module;

(d) receiving and identifying the multicast data packets at the identified ingress port as the expected data;

(e) accessing and using only the MFIB to route the received multicast data packets; and

(f) dropping packets received at the identified physical ingress port that are not identified as expected data.

6. The data router of claim 5 wherein the operating protocol followed is protocol independent multicast (PIM).

7. The data router of claim 5 wherein the MFIB is periodically updated at their client processors by the control processor.

8. The data router of claim 5 connected to and operating on the Internet network.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2016
From: SHERWOOD PARTNERS INC
To: VALENCE TECHNOLOGY INC
Reel/Frame 040091/0829 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2016
From: PLURIS, INC
To: SHERWOOD PARTNERS INC
Reel/Frame 040092/0984 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 23, 2016
From: VALENCE TECHNOLOGY INC
To: PARITY NETWORKS LLC
Reel/Frame 040094/0298 →
Continuity (4)
Continuation 10104904 · Mar 21, 2002
Continuation In Part 09854234 · May 10, 2001
Continuation In Part 09800678 · Mar 6, 2001
Related Publication 20130208720A1 · Aug 15, 2013