IP Library Granted Patent US 8,855,118
Granted Patent B2
US 8,855,118 · App. 13/626,571 · Granted Oct 7, 2014

Source discovery for non-flooding multicast using openflow

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 8,855,118
App. No.
13/626,571
Granted
Oct 7, 2014
Kind
B2
Abstract

Provided is a method of source discovery for non-flooding multicast using OpenFlow. A data packet is received from a source address on a network device. The data packet is routed from the network device to an OpenFlow controller. The OpenFlow controller identifies a rendezvous point (RP) of the network device, maps a random address to the source address in a port used for connecting with the rendezvous point (RP), generates a flow message containing a rule for handling the data packet, transmits the flow message to the network device and adds a flow entry in the network device based on the rule for handling the data packet.

Claims (36)

1. A method of source discovery for non-flooding multicast using OpenFlow, comprising:

receiving a data packet from a source address on a network device;

routing the data packet from the network device to an OpenFlow controller;

identifying a rendezvous point (RP) of the network device in the OpenFlow controller;

mapping a random address to the source address in a port used for to connecting with the rendezvous point (RP) in the OpenFlow controller;

generating a flow message containing a rule for handling the data packet in the OpenFlow controller;

transmitting the flow message to the network device; and

adding a flow entry in the network device based on the rule for handling the data packet.

2. The method of claim 1 , further comprising routing a subsequent data packet from the source address based on the flow entry in the network device.

3. The method of claim 1 , further comprising identifying a subnet of the port used for connecting with the rendezvous point (RP) in the OpenFlow controller.

4. The method of claim 3 , wherein mapping of the random address to the source address occurs in the subnet of the port used for connecting with the rendezvous point (RP).

5. The method of claim 1 , wherein mapping of the random address to the source address is performed using a data structure.

6. The method of claim 5 , wherein the data structure is a hash table.

7. The method of claim 1 , further comprising identifying the port used for connecting with the rendezvous point (RP) in the OpenFlow controller.

8. A network system, comprising:

a network device to receive a data packet from a source address; and

an OpenFlow controller to:

receive the data packet from the network device;

identify a rendezvous point (RP) of the network device;

map a random address to the source address in a port used for connecting with the rendezvous point (RP);

generate a flow message containing a rule for handling the data packet;

transmit the flow message to the network device; and

add a flow entry in the network device based on the rule for handling the data packet.

9. The system of claim 8 , wherein a subsequent data packet is routed from the source address based on the flow entry in the network device.

10. The system of claim 8 , further comprising a port-RP information base module to identify a subnet of the port used for connecting with the rendezvous point (RP) in the OpenFlow controller.

11. The system of claim 10 , wherein the port-RP information base module maps the random address to the source address occurs in the subnet of the port used for connecting with the rendezvous point (RP).

12. The system of claim 8 , wherein the data packet is forwarded to the OpenFlow controller if a reverse path forwarding check on the data packet fails at the network device.

13. The system of claim 8 , wherein the data packet is a first data packet from the source address to the network device.

14. The system of claim 8 , wherein the flow entry in the network device specifies a network route of the data packet.

15. A non-transitory computer readable medium, the non-transitory computer readable medium comprising machine executable instructions, the machine executable instructions when executed by a computer system causes the computer system to:

receive a data packet from a source address on a network device;

identify a rendezvous point (RP) of the network device;

map a random address to the source address in a port used for connecting with the rendezvous point (RP);

generate a flow message containing a rule for handling the data packet;

transmit the flow message to the network device; and

add a flow entry in the network device based on the rule for handling the data packet.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 22, 2021
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP; HEWLETT PACKARD ENTERPRISE COMPANY
To: VALTRUS INNOVATIONS LIMITED
Reel/Frame 055360/0424 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 22, 2012
From: KANNAN, MADHU PRASHANTH
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 029165/0439 →