IP Library Granted Patent US 7,477,612
Granted Patent B2
US 7,477,612 · App. 10/351,517 · Granted Jan 13, 2009

Topology discovery process and mechanism for a network of managed devices

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 7,477,612
App. No.
10/351,517
Granted
Jan 13, 2009
Kind
B2
Abstract

A process of discovering a topology of devices on a network is disclosed. A discover frame is sent to nodes in communication with a central processing unit, with the discover frame having an identification list. After a response frame from the nodes is received, the response frame is processed to determine whether a node sending the response frame has an identification value. If the node has the identification value, then a routing table is updated. When the node does not have the identification value, an identification assign frame is sent to the node and an identification assign acknowledgement frame is received from the node.

Claims (90)

1. A process of discovering a topology of devices on a network, said process comprising:

sending a discover frame having an identification list to nodes in communication with a central processing unit;

awaiting a response frame from said nodes;

processing said response frame to determine whether a node sending the response frame has an identification value;

updating a routing table when the node has the identification value;

sending an identification assign frame to the node when the node does not have the identification value; and

awaiting an identification assign acknowledgement frame from the node when the node does not have the identification value.

2. A process as recited in claim 1 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said step of sending a discover frame comprises sending a discover frame having said source device identifier included therein.

3. A process as recited in claim 1 , wherein said step of sending a discover frame comprises sending a discover frame having number of hops field included therein indicating a number of nodes that the discover frame has passed through.

4. A process as recited in claim 3 , wherein said step of sending a discover frame comprises starting a discovery timer when the discover frame is sent and the process further comprises stopping the process when the discovery timer reaches a predetermined value.

5. A process as recited in claim 4 , wherein said step of processing said response frame comprises reviewing an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover message and the process further comprises changing said predetermined value based on the explosion factor.

6. A process as recited in claim 1 , wherein said step of processing said response frame comprises reviewing an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover frame.

7. A process of discovering a topology of devices on a network, said process comprising:

receiving a discover frame having an identification list by a node from a central processing unit;

checking to see whether an identification value is set;

sending a response to the central processing unit;

forwarding the discover frame to all ports of the node that have not received a separate discovery frame when the identification value is set;

comparing said identification value with frame identification values in the discovery frame; and

dropping the discovery frame when said identification value matches one of the frame identification values in the discovery frame.

8. A process as recited in claim 7 further comprising updating a routing table with route information from the discover frame when the identification value is set.

9. A process as recited in claim 8 , wherein said step of updating a routing table comprises:

adding the route information to information in the routing table;

sorting all entries of the routing table according to number of nodes that are passed through to reach a destination; and

setting as an active route an entry of the routing table having a smallest number of nodes that are passed through for said destination.

10. A process as recited in claim 7 further comprising, when the identification value is set:

awaiting an identification assign frame from the central processing unit;

sending an identification assign acknowledgement frame to the central processing unit;

forwarding the discover frame to all ports of the node that have not received a separate discovery frame; and

updating a routing table with route information from the discover frame.

11. A process as recited in claim 7 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said step of receiving a discover frame comprises receiving a discover frame having said source device identifier included therein.

12. A mechanism for discovering a topology of devices on a network, said mechanism comprising:

first sending means for sending a discover frame having an identification list to nodes in communication with a central processing unit;

first waiting means for awaiting a response frame from said nodes;

processing means for processing said response frame to determine whether a node sending the response frame has an identification value;

updating means for updating a routing table when the node has the identification value;

second sending means for sending an identification assign frame to the node when the node does not have the identification value; and

second waiting means for awaiting an identification assign acknowledgement frame from the node when the node does not have the identification value.

13. A mechanism as recited in claim 12 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said first sending means comprises third sending means for sending a discover frame having said source device identifier included therein.

14. A mechanism as recited in claim 12 , wherein said first sending means comprises third sending means for sending a discover frame having number of hops field included therein indicating the number of nodes that the discover frame has passed through.

15. A mechanism as recited in claim 14 , wherein said third sending means for sending a discover frame comprises starting means for starting a discovery timer when the discover frame is sent and the mechanism further comprises stopping means for stopping the process when the discovery timer reaches a predetermined value.

16. A mechanism as recited in claim 15 , wherein said processing means comprises reviewing means for reviewing an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover message and the mechanism further comprises changing means for changing said predetermined value based on the explosion factor.

17. A mechanism as recited in claim 12 , wherein said processing means comprises reviewing means for reviewing an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover frame.

18. A mechanism for discovering a topology of devices on a network, said mechanism comprising:

receiving means for receiving a discover frame having an identification list by a node from a central processing unit;

checking means for checking to see whether an identification value is set;

sending means for sending a response to the central processing unit; and

forwarding means for forwarding the discover frame to all ports of the node that have not received a separate discovery frame when the identification value is not set;

comparing means for comparing said identification value with frame identification values in the discovery frame; and

dropping means for dropping the discovery frame when said identification value matches one of the frame identification values in the discovery frame.

19. A mechanism as recited in claim 18 further comprising updating means for updating a routing table with route information from the discover frame when the identification value is set.

20. A mechanism as recited in claim 19 , wherein said updating means comprises:

adding means for adding the route information to information in the routing table;

sorting means for sorting all entries of the routing table according to number of nodes that are passed through to reach a destination; and

setting means for setting as an active route an entry of the routing table having a smallest number of nodes that are passed through for said destination.

21. A mechanism as recited in claim 18 further comprising, when the identification value is set:

waiting means for awaiting an identification assign frame from the central processing unit;

second sending means for sending an identification assign acknowledgement frame to the central processing unit;

second forwarding means for forwarding the discover frame to all ports of the node that have not received a separate discovery frame; and

updating means for updating a routing table with route information from the discover frame.

22. A mechanism as recited in claim 18 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said receiving means comprises receiving means for receiving a discover frame having said source device identifier included therein.

23. A mechanism for discovering a topology of devices on a network, said mechanism comprising:

a first sender, configured to send a discover frame having an identification list to nodes in communication with a central processing unit;

a timer, configured to await a response frame from said nodes;

a processor, configured to process said response frame to determine whether a node sending the response frame has an identification value;

a memory interface, configured to update a routing table when the node has the identification value;

a second sender, configured to send an identification assign frame to the node when the node does not have the identification value; and

a acknowledgement timer, configured to await an identification assign acknowledgement frame from the node when the node does not have the identification value.

24. A mechanism as recited in claim 23 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said first sender comprises a third sender configured to send a discover frame having said source device identifier included therein.

25. A mechanism as recited in claim 23 , wherein said first sender comprises a third sender configured to send a discover frame having number of hops field included therein indicating the number of nodes that the discover frame has passed through.

26. A mechanism as recited in claim 25 , wherein said third sender comprises a starter, configured to start the timer when the discover frame is sent and the mechanism further comprises an interrupter, configured to stop the discovery mechanism when the discovery timer reaches a predetermined value.

27. A mechanism as recited in claim 26 , wherein said processor comprises a reviewer configured to review an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover message and the mechanism further comprises a timer reset configured to change said predetermined value based on the explosion factor.

28. A mechanism as recited in claim 23 , wherein said processor comprises a reviewer configured to review an explosion factor contained in the response frame, where the explosion factor is related to a number of ports on the node that have not received a separate discover frame.

29. A mechanism for discovering a topology of devices on a network, said mechanism comprising:

a receiver, configured to receive a discover flame having an identification list by a node from a central processing unit;

a checker, configured to check to see whether an identification value is set;

a sender, configured to send a response to the central processing unit; and

a transmitter, configured to forward the discover flame to all ports of the node that have not received a separate discovery flame when the identification value is not set;

a comparator, configured to compare said identification value with frame identification values in the discovery frame; and

a deletion mechanism, configured to drop the discovery frame when said identification value matches one of the frame identification values in the discovery frame.

30. A mechanism as recited in claim 29 further comprising an updater configured to update a routing table with route information from the discover frame when the identification value is set.

31. A mechanism as recited in claim 30 , wherein said updater comprises:

an adder, configured to add the route information to information in the routing table;

a sorter, configured to sort all entries of the routing table according to number of nodes that are passed through to reach a destination; and

a setter, configured to set as an active route an entry of the routing table having a smallest number of nodes that are passed through for said destination.

32. A mechanism as recited in claim 29 further comprising:

a timer, configured to await an identification assign frame from the central processing unit;

a second sender configured to send an identification assign acknowledgement frame to the central processing unit;

a transmitter, configured to forward the discover frame to all ports of the node that have not received a separate discovery frame; and

an updater, configured to update a routing table with route information from the discover frame.

33. A mechanism as recited in claim 29 , wherein said central processing unit comprises a system management central processing unit having a source device identifier and said receiver comprises a receiver configured to receive a discover frame having said source device identifier included therein.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE ERROR IN RECORDING THE MERGER PREVIOUSLY RECORDED AT REEL: 047357 FRAME: 0302. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Mar 22, 2019
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 048674/0834 →
CORRECTIVE ASSIGNMENT TO CORRECT THE EFFECTIVE DATE OF MERGER PREVIOUSLY RECORDED ON REEL 047195 FRAME 0658. ASSIGNOR(S) HEREBY CONFIRMS THE THE EFFECTIVE DATE IS 09/05/2018. Recorded Oct 29, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047357/0302 →
MERGER Recorded Oct 4, 2018
From: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047195/0658 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Feb 3, 2017
From: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
To: BROADCOM CORPORATION
Reel/Frame 041712/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2017
From: BROADCOM CORPORATION
To: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.
Reel/Frame 041706/0001 →
PATENT SECURITY AGREEMENT Recorded Feb 11, 2016
From: BROADCOM CORPORATION
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 037806/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 10, 2003
From: SHANKAR, LAXMAN
To: BROADCOM CORPORATION
Reel/Frame 013789/0648 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 27, 2003
From: SHANNKAR, LAXMAN
To: BROADCOM CORPORATION
Reel/Frame 013708/0187 →