Methods and systems for using managed port circuitry to map connections among structured cabling apparatus and network devices

• US 8,165,014 B2
• Filed: 06/19/2008
• Issued: 04/24/2012
• Est. Priority Date: 06/19/2007
• Status: Expired due to Fees

• Current Assignee: Commscope Inc of North Carolina (CommScope Holding Company, Inc.)
• Original Assignee: Commscope Inc of North Carolina (CommScope Holding Company, Inc.)
• Inventors: Brooks, George, Sumrall, Jeffrey, Cobb, Terry, Choudhury, G. Mabud, Enge, Ryan
• Primary Examiner(s): Moe, Aung S
• Assistant Examiner(s): Elliott, IV, Benjamin H
• Application Number:
  US12/142,542
• Publication Number:
  US 20080316940A1
• Time in Patent Office: 1,405 Days
• Field of Search: 370/245, 370/248, 370/254, 370/256, 370/285, 370/355, 370/357, 370218-220, 370/225, 370/228, 379/29.04, 379/29.08, 379/32.01, 379/92.01, 379/442, 710/312, 714/25, 714 36- 37, 714/47.1, 398 1- 3, 398/10, 398/12, 398 55- 57
• US Class Current: 370/218
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0273 using web services for network management, e.g. simple object access protocol [SOAP]
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 43/0811 by checking connectivity
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A managed port circuit includes a detection circuit that is disposed in a communication channel between a first local port and a second local port and a controller that is coupled to the detection circuit and is operable to configure the detection circuit in a detection configuration in which the first and second local ports are connected to the controller and a second pass through configuration in which the first and second local ports are connected to each other via the communication channel, the controller being further operable to determine when an end device is connected to one of the first and second local ports when the detection circuit is in the detection configuration.

Claims

1. A managed port circuit, comprising:

a detection circuit that is disposed in a communication channel between a first local port and a second local port; and

a controller that is coupled to the detection circuit and is operable to configure the detection circuit in a detection configuration in which the first and second local ports, the detection circuit, and the controller are connected in series via the communication channel and a second pass through configuration in which the first and second local ports are connected to each other via the communication channel without the communication channel passing through the controller and the detection circuit, the controller being further operable to determine when an end device is connected to one of the first and second local ports when the detection circuit is in the detection configuration.

2. The managed port circuit of claim 1, further comprising:

an interface circuit that connects the detection circuit to the controller and is operable to report end device connections to the first and second local ports to the controller.

3. The managed port circuit of claim 1, further comprising:

a disconnection detection circuit that is connected between the controller and the first and second local ports and is operable to report end device disconnections from the first and second local ports to the controller.

4. The managed port circuit of claim 3, wherein the disconnection detection circuit is a differential current sense or voltage sense amplifier circuit.

5. The managed port circuit of claim 1, wherein the detection circuit comprises an electrical relay circuit, an analog switch Integrated Circuit (IC), an optical relay circuit, and/or an electromechanical switch circuit.

6. The managed port circuit of claim 1, wherein the detection circuit comprises a network switch Integrated Circuit (IC).

7. The managed port circuit of claim 6, wherein the first and second local ports are part of a Virtual Local Area Network (VLAN).

8. The managed port circuit of claim 1, wherein the controller is further operable to determine a type of end device connected to one of the first and second local ports, a port number for the first or second local port that the end device is connected to, a port number on the end device that the first or second local port is connected to, a physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, a physical location of the local device, connection status of the end device, and/or a Medium Access Control (MAC) address associated with the end device.

9. The managed port circuit of claim 8, wherein the type of end device comprises a patch panel, a zone/cp box, a wall outlet, Data Terminal Equipment (DTE) and/or a network bridge device.

10. The managed port circuit of claim 9, wherein the network bridge device comprises a network switch, router, and/or hub.

11. The managed port circuit of claim 8, wherein the controller is further operable to determine the type of end device by transmitting Port Info packets during an end device detection time interval and determining if a Port Info Response packet is received and/or a Port Info packet is received.

12. The managed port circuit of claim 11, wherein the controller is further operable to determine that the end device type is a wall outlet or patch panel when a Port Info packet or Port Info Response packet is received.

13. The managed port circuit of claim 8, wherein the controller is further operable to determine the type of end device by determining if a Spanning Tree packet is received and/or an Ethernet packet is received other than a Spanning Tree packet.

14. The managed port circuit of claim 13, wherein the controller is further operable to determine that the end device is a network bridge device if the Spanning Tree packet is received.

15. The managed port circuit of claim 13, wherein the Spanning Tree packet comprises a Spanning Tree Protocol (STP) packet, Rapid Spanning Tree Protocol (RSTP) packet, Multiple Spanning Tree Protocol (MSTP) packet, Per-VLAN Spanning Tree (PVST) protocol packet, and/or Rapid Per-VLAN Spanning Tree (R-PVST) protocol packet.

16. The managed port circuit of claim 8, wherein the controller is further operable to configure the detection circuit in the pass through configuration after determining the types of devices connected to the first and second local ports.

17. The managed port circuit of claim 8, wherein the controller is further configured to communicate the type of end device connected to one of the first and second local ports, the port number for the first or second local port that the end device is connected to, the physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, the physical location of the local device, connection status of the end device, and/or the Medium Access Control (MAC) address associated with the end device to a network monitoring system.

18. The managed port circuit of claim 1, wherein the detection circuit is disposed in a patch panel, zone/cp box, or wall outlet.

19. The managed port circuit of claim 18, wherein the controller is disposed in the patch panel, zone/cp box, or wall outlet.

20. The managed port circuit of claim 1, wherein a communication medium connecting the end device to one of the first and second local ports lacks a dedicated connectivity control channel.

21. The managed port circuit of claim 20, wherein the communication channel comprises an electrical cable including four wire pairs.

22. The managed port circuit of claim 20, wherein the communication channel comprises a plurality of optical fibers.

23. A method of operating a communication network, comprising:

providing a detection circuit in a communication channel between a first local port and a second local port;

configuring the detection circuit in a detection configuration in which the first local port is connected to the second local port via a controller and the detection circuit such that the first and second local ports, the detection circuit, and the controller are connected in series, the controller being configured to determine when the first and second local ports have end devices connected thereto; and

configuring the detection circuit in a pass through configuration in which the first and second local ports are connected to each other without the controller and the detection circuit after the controller determines that the first and second local ports have end devices connected thereto.

24. The method of claim 23, further comprising:

determining at the controller a type of end device connected to one of the first and second local ports, a port number for the first or second local port that the end device is connected to, a port number on the end device that the first or second local port is connected to, a physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, a physical location of the local device, connection status of the end device, and/or a Medium Access Control (MAC) address associated with the end device.

25. The method of claim 24, wherein the type of end device comprises a patch panel, a zone/cp box, a wall outlet, Data Terminal Equipment (DTE) and/or a network bridge device.

26. The method of claim 25, wherein the network bridge device comprises a network switch, router, and/or hub.

27. The method of claim 25, further comprising:

transmitting Port Info packets from the controller to the first and second local ports during an end device detection time interval; and

determining at the controller if a Port Info Response packet is received and/or a Port Info packet is received.

28. The method of claim 27, further comprising:

determining at the controller that the end device type is a wall outlet or patch panel when a Port Info packet or Port Info Response packet is received.

29. The method of claim 25, further comprising:

determining at the controller if a Spanning Tree packet is received and/or an Ethernet packet is received other than a Spanning Tree packet.

30. The method of claim 29, further comprising:

determining at the controller that the end device type is a network bridge device if the Spanning Tree packet is received.

31. The method of claim 29, wherein the Spanning Tree packet comprises a Spanning Tree Protocol (STP) packet, Rapid Spanning Tree Protocol (RSTP) packet, Multiple Spanning Tree Protocol (MSTP) packet, Per-VLAN Spanning Tree (PVST) protocol packet, and/or Rapid Per-VLAN Spanning Tree (R-PVST) protocol packet.

32. The method of claim 24, further comprising:

communicating the type of end device connected to one of the first and second local ports, the port number for the first or second local port that the end device is connected to, the physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, the physical location of the local device, connection status of the end device, and/or the Medium Access Control (MAC) address associated with the end device to a network monitoring system.

33. A managed port circuit, comprising:

a detection circuit; and

a controller that is coupled to the detection circuit and is operable to switch the detection circuit between a detection configuration in which a first local port is connected to a second local port via the detection circuit and the controller to monitor traffic on the communication channel and to determine when an end device is connected to one of the first and second local ports such that the first and second local ports, the detection circuit and the controller are connected in series via a communication channel and a pass through configuration in which the first and second local ports are connected to each other without the controller and the detection circuit.

34. The managed port circuit of claim 33, wherein the detection circuit comprises a network switch Integrated Circuit (IC).

35. The managed port circuit of claim 34, wherein the first and second local ports are part of a Virtual Local Area Network (VLAN).

36. The managed port circuit of claim 33, wherein the controller is further operable to determine a type of end device connected to one of the first and second local ports, a port number for the first or second local port that the end device is connected to, a port number on the end device that the first or second local port is connected to, a physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, a physical location of the local device, connection status of the end device, and/or a Medium Access Control (MAC) address associated with the end device.

37. The managed port circuit of claim 36, wherein the type of end device comprises a patch panel, a zone/cp box, a wall outlet, Data Terminal Equipment (DTE) and/or a network bridge device.

38. The managed port circuit of claim 37, wherein the network bridge device comprises a network switch, router, and/or hub.

39. The managed port circuit of claim 36, wherein the controller is further operable to determine the type of end device by transmitting Port Info packets during an end device detection time interval and determining if a Port Info Response packet is received and/or a Port Info packet is received.

40. The managed port circuit of claim 39, wherein the controller is further operable to determine that the end device type is a wall outlet or patch panel when a Port Info packet or Port Info Response packet is received.

41. The managed port circuit of claim 36, wherein the controller is further operable to determine the type of end device by determining if a Spanning Tree packet is received and/or an Ethernet packet is received other than a Spanning Tree packet.

42. The managed port circuit of claim 41, wherein the controller is further operable to determine that the end device is a network bridge device if the Spanning Tree packet is received.

43. The managed port circuit of claim 42, wherein the Spanning Tree packet comprises a Spanning Tree Protocol (STP) packet, Rapid Spanning Tree Protocol (RSTP) packet, Multiple Spanning Tree Protocol (MSTP) packet, Per-VLAN Spanning Tree (PVST) protocol packet, and/or Rapid Per-VLAN Spanning Tree (R-PVST) protocol packet.

44. The managed port circuit of claim 36, wherein the controller is further configured to communicate the type of end device connected to one of the first and second local ports, the port number for the first or second local port that the end device is connected to, the physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, the physical location of the local device, connection status of the end device, and/or the Medium Access Control (MAC) address associated with the end device to a network monitoring system.

45. The managed port circuit of claim 33, wherein the detection circuit is disposed in a patch panel, zone/cp box, or wall outlet.

46. The managed port circuit of claim 45, wherein the controller is disposed in the patch panel, zone/cp box, or wall outlet.

47. The managed port circuit of claim 33, wherein a communication medium connecting the end device to one of the first and second local ports lacks a dedicated connectivity control channel.

48. The managed port circuit of claim 47, wherein the communication channel comprises an electrical cable including four wire pairs.

49. The managed port circuit of claim 47, wherein the communication channel comprises a plurality of optical fibers.

50. A method of operating a communication network, comprising:

providing a detection circuit; and

monitoring traffic on the communication channel via a controller that is coupled to the detection circuit and is operable to switch the detection circuit between a detection configuration in which a first local port is connected to a second local port via the detection circuit and the controller to determine when an end device is connected to one of the first and second local ports such that the first and second local ports, the detection circuit and the controller are connected in series via a communication channel and a pass through configuration in which the first and second local ports are connected to each other without the controller and the detection circuit.

51. The method of claim 50, further comprising:

determining at the controller a type of end device connected to one of the first and second local ports, a port number for the first or second local port that the end device is connected to, a port number on the end device that the first or second local port is connected to, a physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, a physical location of the local device, connection status of the end device, and/or a Medium Access Control (MAC) address associated with the end device.

52. The method of claim 51, wherein the type of end device comprises a patch panel, a zone/cp box, a wall outlet, Data Terminal Equipment (DTE) and/or a network bridge device.

53. The method of claim 52, wherein the network bridge device comprises a network switch, router, and/or hub.

54. The method of claim 52, further comprising:

transmitting Port Info packets from the controller to the first and second local ports during an end device detection time interval; and

determining at the controller if a Port Info Response packet is received and/or a Port Info packet is received.

55. The method of claim 54, further comprising:

determining at the controller that the end device type is a wall outlet or patch panel when a Port Info packet or Port Info Response packet is received.

56. The method of claim 52, further comprising:

determining at the controller if a Spanning Tree packet is received and/or an Ethernet packet is received other than a Spanning Tree packet.

57. The method of claim 56, further comprising:

determining at the controller that the end device type is a network bridge device if the Spanning Tree packet is received.

58. The method of claim 56, wherein the Spanning Tree packet comprises a Spanning Tree Protocol (STP) packet, Rapid Spanning Tree Protocol (RSTP) packet, Multiple Spanning Tree Protocol (MSTP) packet, Per-VLAN Spanning Tree (PVST) protocol packet, and/or Rapid Per-VLAN Spanning Tree (R-PVST) protocol packet.

59. The method of claim 51, further comprising:

communicating the type of end device connected to one of the first and second local ports, the port number for the first or second local port that the end device is connected to, the physical location of the first or second local port that the end device is connected to on a local device that is associated with the managed port circuit, the physical location of the local device, connection status of the end device, and/or the Medium Access Control (MAC) address associated with the end device to a network monitoring system.