US20190081909A1 - Managed connectivity devices, systems, and methods - Google Patents

Abstract

One exemplary embodiment is directed to an end node comprising a programmable processor configured to execute software and an ETHERNET network interface communicatively coupled to the programmable processor. The network interface is configured to couple the end node to a network. The ETHERNET network interface comprises a media access control device, an ETHERNET physical layer device, and a port to connect a cable to the network interface. The physical layer device comprises an integrated storage-device interface to communicate with a storage device associated with a connector attached to an end of the cable when connected to the network interface via the port. The software is configured to use the integrated storage-device interface to read information stored in the storage device and to communicate the read information over the network.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• This application is a continuation application of U.S. patent application Ser. No. 12/705,514, filed Feb. 12, 2010, which is hereby incorporated herein by reference and which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/152,624, filed Feb. 13, 2009, which is hereby incorporated herein by reference.
BACKGROUND
• Communication networks typically include numerous logical communication links between various items of equipment. Often a single logical communication link is implemented using several pieces of physical communication media. For example, a logical communication link between a computer and an inter-networking device such as a hub or router can be implemented as follows. A first cable connects the computer to a jack mounted in a wall. A second cable connects the wall-mounted jack to a port of a patch panel, and a third cable connects the inter-networking device to another port of a patch panel. A “patch cord” cross connects the two together. In other words, a single logical communication link is often implemented using several segments of physical communication media.
• A network or enterprise management system (generally referred to here as a “network management system” or “NMS”) is typically aware of the logical communication links that exist in a network but typically does not have information about the specific physical layer media that are used to implement the logical communication links. Indeed, NMS systems typically do not have the ability to display or otherwise provide information about how logical communication links are implemented at the physical layer level.
• Physical layer management (PLM) systems do exist. However, existing PLM systems are typically designed to facilitate the adding, changing, and removing of cross connections at a particular patch panel or a set of patch panels at a given location. Generally, such PLM systems include functionality to track what is connected to each port of a patch panel, trace connections that are made using a patch panel, and provide visual indications to a user at a patch panel. However, such PLM systems are typically “patch-panel” centric in that they are focused on helping a technician correctly add, change, or remove cross connections at a patch panel. Any “intelligence” included in or coupled to the patch panel is typically only designed to facilitate making accurate cross connections at the patch panel and trouble shooting related problems (for example, by detecting whether a patch cord is inserted into a given port and/or by determining which ports are coupled to one another using a patch cord).
• Moreover, any information that such PLM systems collect is typically only used within the PLM systems. In other words, the collections of information that such PLM systems maintain are logical “islands” that are not used at the application-layer level by other systems. Though such PLM systems are sometimes connected to other networks (for example, connected to local area networks or the Internet), such network connections are typically only used to enable a user to remotely access the PLM systems. That is, a user remotely accesses the PLM-related application-layer functionality that resides in the PLM system itself using the external network connection but external systems or networks typically do not themselves include any application-layer functionality that makes use of any of the physical-layer-related information that resides in the PLM system.
SUMMARY
• One exemplary embodiment is directed to an end node comprising an interface to couple the end node to a network. The interface comprising a port to attach to a segment of physical communication media. The end node further includes a programmable processor configured to execute software. The software comprises physical layer information (PLI) functionality. The PLI functionality is configured to read information stored on or in the segment of physical communication media that is attached to the port and to communicate the read information over the network (for example, to an aggregation point).
• Another exemplary embodiment is directed to a wall outlet comprising at least one port to connect to at least one segment of physical communication media. The wall outlet is configured to read information stored on or in the segment of physical communication media connected to the wall outlet. The wall outlet is configured to communicate at least a portion of the information read from the segment of physical communication media to an aggregation point.
• Another exemplary embodiment is directed to a wall outlet comprising a plurality of downstream ports, at least one upstream port, and a switch communicatively coupled to the downstream ports and the at least one upstream port. The wall outlet is configured to read information stored on or in physical communication media that is connected to the ports and to communicate the read information over the at least one upstream port (for example, to an aggregation point).
• The details of various embodiments of the claimed invention are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.
DRAWINGS
• FIG. 1 is a block diagram of one exemplary embodiment of a system that includes physical layer information (PLI) functionality as well as physical layer management (PLM) functionality.
• FIG. 2 is a block diagram of one high-level embodiment of a port and media reading interface that are suitable for use in the system ofFIG. 1.
• FIG. 3 illustrates one exemplary embodiment of a system that includes physical layer information (PLI) functionality as well as physical layer management (PLM) functionality.
• FIG. 4 is a block diagram of one exemplary embodiment of each slave processor module shown inFIG. 3.
• FIG. 5 is a block diagram of one embodiment of the master processor unit ofFIG. 3.
• FIG. 6 is a diagram illustrating one embodiment of a patch cord that is suitable for use in the system ofFIG. 3.
• FIG. 7 is a diagram illustrating another exemplary embodiment of a patch cord that is suitable for use in the system ofFIG. 3.
• FIG. 8 is a block diagram of one embodiment of an aggregation point.
• FIG. 9 is a block diagram of one embodiment of a network management system (NMS) that is specially configured to use the physical layer information that is captured and aggregated using the techniques described here.
• FIG. 10 is a flow diagram of one exemplary embodiment of a method of compliance tracking in a network that includes the physical layer information functionality.
• FIG. 11 is a block diagram of one embodiment of an inter-networking device that is specially configured to use physical layer information that is captured and aggregated using the techniques described here.
• FIG. 12 illustrates an example of how physical layer information that is captured and aggregated using the techniques described here can be used to improve the efficiency of the inter-networking devices used in a network.
• FIG. 13 illustrates another exemplary embodiment of a system that includes physical layer information functionality as well as physical layer management functionality.
• FIGS. 14-16 illustrate another exemplary embodiment of a system that includes physical layer information functionality as well as physical layer management functionality.
• FIG. 17 is a block diagram of one embodiment of a wall outlet that includes functionality to obtain physical layer information.
• FIG. 18 is one embodiment of a computer that includes functionality to obtain physical layer information.
• FIG. 19 is a block diagram of one exemplary embodiment of a switch that uses a physical layer device that includes integrated functionality for reading media information.
• FIG. 20 is a block diagram of one exemplary embodiment of a computer that uses a physical layer device that includes integrated functionality for reading media information.
• FIG. 21 is a diagram of one embodiment of a jacket that can be fitted around an RJ-45 plug in order to attach a storage device to the RJ-45 plug.
• FIG. 22 illustrates a network deploying passive fiber optic lines.
• FIG. 23 is a schematic diagram showing an example cable routing scheme for the fiber distribution hubs ofFIG. 23.
• Like reference numbers and designations in the various drawings indicate like elements.
DETAILED DESCRIPTION
• FIG. 1 is a block diagram of one embodiment of asystem100 that includes physical layer information (PLI) functionality as well as physical layer management (PLM) functionality. Thesystem100 comprises a plurality ofconnector assemblies102, where eachconnector assembly102 comprises one ormore ports104. In general, theconnector assemblies102 are used to attach segments of physical communication media to one another.
• Each segment of physical communication media is attached to arespective port104. Eachport104 is used to connect two or more segments of physical communication media to one another (for example, to implement a portion of a logical communication link). Examples ofconnector assemblies102 include, for example, rack-mounted connector assemblies (such as patch panels, distribution units, and media converters for fiber and copper physical communication media), wall-mounted connector assemblies (such as boxes, jacks, outlets, and media converters for fiber and copper physical communication media), and inter-networking devices (such as switches, routers, hubs, repeaters, gateways, and access points).
• At least some of theconnector assemblies102 are designed for use with segments of physical communication media that have identifier and attribute information stored in or on them. The identifier and attribute information is stored in or on the segment of physical communication media in a manner that enables the stored information, when the segment is attached to aport104, to be read by aprogrammable processor106 associated with theconnector assembly102. Examples of information that can be stored in or on a segment of physical communication media include, without limitation, an identifier that uniquely identifies that particular segment of physical communication media (similar to an ETHERNET Media Access Control (MAC) address but associated with the physical communication media and/or connector attached to the physical communication media), a part number, a plug or other connector type, a cable or fiber type and length, a serial number, a cable polarity, a date of manufacture, a manufacturing lot number, information about one or more visual attributes of physical communication media or a connector attached to the physical communication media (such as information about the color or shape of the physical communication media or connector or an image of the physical communication media or connector), and other information used by an Enterprise Resource Planning (ERP) system or inventory control system. In other embodiments, alternate or additional data is stored in or on the media segments. For example, testing or media quality or performance information can be stored in or on the segment of physical communication media. The testing or media quality or performance information, for example, can be the results of testing that is performed when a particular segment of media is manufactured.
• Also, as noted below, in some embodiments, the information stored in or on the segment of physical communication media can be updated. For example, the information stored in or on the segment of physical communication media can be updated to include the results of testing that is performed when a segment of physical media is installed or otherwise checked. In another example, such testing information is supplied to anaggregation point120 and stored in a data store maintained by the aggregation point120 (both of which are described below). In another example, the information stored in or on the segment of physical communication media includes a count of the number of times that a connector (not shown) attached to a segment of physical communication media has been inserted intoport104. In such an example, the count stored in or on the segment of physical communication media is updated each time the connector is inserted intoport104. This insertion count value can be used, for example, for warranty purposes (for example, to determine if the connector has been inserted more than the number of times specified in the warranty) or for security purposes (for example, to detect unauthorized insertions of the physical communication media).
• In the particular embodiment shown inFIG. 1, each of theports104 of theconnector assemblies102 comprises a respectivemedia reading interface108 via which the respectiveprogrammable processor106 is able to determine if a physical communication media segment is attached to thatport104 and, if one is, to read the identifier and attribute information stored in or on the attached segment (if such information is stored therein or thereon). Theprogrammable processor106 associated with eachconnector assembly102 is communicatively coupled to each of the media reading interfaces108 using a suitable bus or other interconnect (not shown).
• In the particular embodiment shown inFIG. 1, four exemplary types of connector assembly configurations are shown. In the first connector assembly configuration110 shown inFIG. 1, eachconnector assembly102 includes its own respectiveprogrammable processor106 and its ownrespective network interface116 that is used to communicatively couple thatconnector assembly102 to an Internet Protocol (IP)network118.
• In the second type of connector assembly configuration112, a group ofconnector assemblies102 are physically located near each other (for example, in a bay or equipment closet). Each of theconnector assemblies102 in the group includes its own respectiveprogrammable processor106. However, in the second connector assembly configuration112, some of the connector assemblies102 (referred to here as “interfaced connector assemblies”) include their ownrespective network interfaces116 while some of the connector assemblies102 (referred to here as “non-interfaced connector assemblies”) do not. Thenon-interfaced connector assemblies102 are communicatively coupled to one or more of the interfacedconnector assemblies102 in the group via local connections. In this way, thenon-interfaced connector assemblies102 are communicatively coupled to theIP network118 via thenetwork interface116 included in one or more of the interfacedconnector assemblies102 in the group. In the second type of connector assembly configuration112, the total number ofnetwork interfaces116 used to couple theconnector assemblies102 to theIP network118 can be reduced. Moreover, in the particular embodiment shown inFIG. 1, thenon-interfaced connector assemblies102 are connected to the interfacedconnector assembly102 using a daisy chain topology (though other topologies can be used in other implementations and embodiments).
• In the third type of connector assembly configuration114, a group ofconnector assemblies102 are physically located near each other (for example, within a bay or equipment closet). Some of theconnector assemblies102 in the group (also referred to here as “master” connector assemblies102) include both their ownprogrammable processors106 andnetwork interfaces116, while some of the connector assemblies102 (also referred to here as “slave” connector assemblies102) do not include their ownprogrammable processors106 or network interfaces116. Each of theslave connector assemblies102 is communicatively coupled to one or more of themaster connector assemblies102 in the group via one or more local connections. Theprogrammable processor106 in each of themaster connector assemblies102 is able to carry out the processing described below for both themaster connector assembly102 of which it is a part and anyslave connector assemblies102 to which themaster connector assembly102 is connected via the local connections. As a result, the cost associated with theslave connector assemblies102 can be reduced. In the particular embodiment shown inFIG. 1, theslave connector assemblies102 are connected to amaster connector assembly102 in a star topology (though other topologies can be used in other implementations and embodiments).
• Eachprogrammable processor106 is configured to execute software or firmware that causes theprogrammable processor106 to carry out various functions described below. Eachprogrammable processor106 also includes suitable memory (not shown) that is coupled to theprogrammable processor106 for storing program instructions and data. In general, theprogrammable processor106 determines if a physical communication media segment is attached to aport104 with which thatprocessor106 is associated and, if one is, to read the identifier and attribute information stored in or on the attached physical communication media segment (if the segment includes such information stored therein or thereon) using the associatedmedia reading interface108.
• In the first, second, and third configurations110,112, and114, eachprogrammable processor106 is also configured to communicate physical layer information to devices that are coupled to theIP network118. The physical layer information (PLI) includes information about theconnector assemblies102 associated with that programmable processor106 (also referred to here as “device information”) as well as information about any segments of physical media attached to theports104 of those connector assemblies102 (also referred to here as “media information”) The device information includes, for example, an identifier for each connector assembly, a type identifier that identifies the connector assembly's type, and port priority information that associates a priority level with each port. The media information includes identity and attribute information that theprogrammable processor106 has read from attached physical media segments that have identifier and attribute information stored in or on it. The media information may also include information about physical communication media that does not have identifier or attribute information stored in or on it. This latter type of media information can be manually input at the time the associated physical media segments are attached to the connector assembly102 (for example, using a management application executing on theprogrammable processor106 that enables a user to configure and monitor the connector assembly102).
• In the fourth type of connector assembly configuration115, a group ofconnector assemblies102 are housed within a common chassis or other enclosure. Each of theconnector assemblies102 in the configuration115 includes their ownprogrammable processors106. In the context of this configuration115, theprogrammable processors106 in each of the connector assemblies are “slave”processors106. Each of the slaveprogrammable processor106 is also communicatively coupled to a common “master” programmable processor117 (for example, over a backplane included in the chassis or enclosure). The masterprogrammable processor117 is coupled to anetwork interface116 that is used to communicatively couple the masterprogrammable processor117 to theIP network118. In this configuration115, each slaveprogrammable processor106 is configured to determine if physical communication media segments are attached to itsport104 and to read the identifier and attribute information stored in or on the attached physical communication media segments (if the attached segments have such information stored therein or thereon) using the associated media reading interfaces108. This information is communicated from the slaveprogrammable processor106 in each of theconnector assemblies102 in the chassis to themaster processor117. Themaster processor117 is configured to handle the processing associated with communicating the physical layer information read from by theslave processors106 to devices that are coupled to theIP network118.
• Thesystem100 includes functionality that enables the physical layer information that theconnector assemblies102 capture to be used by application-layer functionality outside of the traditional physical-layer management application domain. That is, the physical layer information is not retained in a PLM “island” used only for PLM purposes but is instead made available to other applications. In the particular embodiment shown inFIG. 1, thesystem100 includes anaggregation point120 that is communicatively coupled to theconnector assemblies102 via theIP network118.
• Theaggregation point120 includes functionality that obtains physical layer information from the connector assemblies102 (and other devices) and stores the physical layer information in a data store.
• Theaggregation point120 can be used to receive physical layer information from various types ofconnector assemblies106 that have functionality for automatically reading information stored in or on the segment of physical communication media. Examples ofsuch connector assemblies106 are noted above. Also, theaggregation point120 and aggregation functionality124 can also be used to receive physical layer information from other types of devices that have functionality for automatically reading information stored in or on the segment of physical communication media. Examples of such devices include end-user devices—such as computers, peripherals (such as printers, copiers, storage devices, and scanners), and IP telephones—that include functionality for automatically reading information stored in or on the segment of physical communication media.
• Theaggregation point120 can also be used to obtain other types of physical layer information. For example, in this embodiment, theaggregation point120 also obtains information about physical communication media segments that is not otherwise automatically communicated to anaggregation point120. One example of such information is information about non-connectorized physical communication media segments that do not otherwise have information stored in or on them that are attached to a connector assembly (including, for example, information indicating which ports of the devices are connected to which ports of other devices in the network as well as media information about the segment). Another example of such information is information about physical communication media segments that are connected to devices that are not be able to read media information that is stored in or on the media segments that are attached to their ports and/or that are not able to communicate such information to the aggregation point120 (for example, because such devices do not include such functionality, because such devices are used with media segments that do not have media information stored in or on them, and/or because bandwidth is not available for communicating such information to the aggregation point120). In this example, the information can include, for example, information about the devices themselves (such as the devices' MAC addresses and IP addresses if assigned to such devices), information indicating which ports of the devices are connected to which ports of other devices in the network (for example, other connector assemblies), and information about the physical media attached to the ports of the devices. This information can be provided to theaggregation point120, for example, by manually entering such information into a file (such as a spreadsheet) and then uploading the file to the aggregation point120 (for example, using a web browser) in connection with the initial installation of each of the various items. Such information can also, for example, be directly entered using a user interface provided by the aggregation point120 (for example, using a web browser).
• Theaggregation point120 can also obtain information about the layout of the building or buildings in which the network is deployed, as well as information indicating where eachconnector assembly102, physical media segment, and inter-networking device is located within the building. This information can be, for example, manually entered and verified (for example, using a web browser) in connection with the initial installation of each of the various items. In one implementation, such location information includes an X, Y, and Z location for each port or other termination point for each physical communication media segment (for example, X, Y, and Z location information of the type specified in the ANSI/TIA/EIA 606-A Standard (Administration Standard For The Commercial Telecommunications Infrastructure)).
• Theaggregation point120 can obtain and maintain testing, media quality, or performance information relating to the various segments of physical communication media that exist in the network. The testing, media quality, or performance information, for example, can be results of testing that is performed when a particular segment of media is manufactured and/or when testing is performed when a particular segment of media is installed or otherwise checked.
• Theaggregation point120 also includes functionality that provides an interface for external devices or entities to access the physical layer information maintained by theaggregation point120. This access can include retrieving information from theaggregation point120 as well as supplying information to theaggregation point120. In this embodiment, theaggregation point120 is implemented as “middleware” that is able to provide such external devices and entities with transparent and convenient access to the PLI maintained by theaccess point120. Because theaggregation point120 aggregates PLI from the relevant devices on theIP network118 and provides external devices and entities with access to such PLI, the external devices and entities do not need to individually interact with all of the devices in theIP network118 that provide PLI, nor do such devices need to have the capacity to respond to requests from such external devices and entities.
• Theaggregation point120, in the embodiment shown inFIG. 1, implements an application programming interface (API) by which application-layer functionality can gain access to the physical layer information maintained by theaggregation point120 using a software development kit (SDK) that describes and documents the API.
• For example, as shown inFIG. 1, a network management system (NMS)130 includes physical layer information (PLI)functionality132 that is configured to retrieve physical layer information from theaggregation point120 and provide it to the other parts of theNMS130 for use thereby. TheNMS130 uses the retrieved physical layer information to perform one or more network management functions (for example, as described below). In one implementation of the embodiment shown inFIG. 1, thePLI functionality132 of theNMS130 retrieves physical layer information from theaggregation point120 using the API implemented by theaggregation point120. TheNMS130 communicates with theaggregation point120 over theIP network118.
• As shown inFIG. 1, anapplication134 executing on acomputer136 can also use the API implemented by theaggregation point120 to access the PLI information maintained by the aggregation point120 (for example, to retrieve such information from theaggregation point120 and/or to supply such information to the aggregation point120). Thecomputer136 is coupled to theIP network118 and accesses theaggregation point120 over theIP network118.
• In the embodiment shown inFIG. 1, one or moreinter-networking devices138 used to implement theIP network118 include physical layer information (PLI)functionality140. ThePLI functionality140 of theinter-networking device138 is configured to retrieve physical layer information from theaggregation point120 and use the retrieved physical layer information to perform one or more inter-networking functions. Examples of inter-networking functions include Layer 1, Layer 2, and Layer 3 (of the OSI model) inter-networking functions such as the routing, switching, repeating, bridging, and grooming of communication traffic that is received at the inter-networking device. In one implementation of such an embodiment, thePLI functionality140 uses the API implemented by theaggregation point120 to communicate with theaggregation point120.
• ThePLI functionality140 included in theinter-networking device138 can also be used to capture physical layer information associated with theinter-network device138 and the physical communication media attached to it and communicate the captured physical layer information to theaggregation point120. Such information can be provided to theaggregation point120 using the API or by using the protocols that are used to communicate with theconnector assemblies102.
• Theaggregation point120 can be implemented on a standalone network node (for example, a standalone computer running appropriate software) or can be integrated along with other network functionality (for example, integrated with an element management system or network management system or other network server or network element). Moreover, the functionality of theaggregation point120 can be distribute across many nodes and devices in the network and/or implemented, for example, in a hierarchical manner (for example, with many levels of aggregation points).
• Moreover, theaggregation point120 and theconnector assemblies102 are configured so that theaggregation point120 can automatically discover and connect with devices that provide PLI to an aggregation point120 (such as theconnector assemblies102 and inter-network device138) that are on thenetwork118. In this way, when devices that are able to provide PLI to an aggregation point120 (such as aconnector assembly102 or an inter-networking device138) are coupled to theIP network118, anaggregation point120 is able to automatically discover theconnector assembly102 and start aggregating physical layer information for thatconnector assembly102 without requiring the person installing theconnector assembly102 to have knowledge of the aggregation points120 that are on the IP network. Similarly, when anaggregation point120 is coupled to theIP network118, theaggregation point120 is able to automatically discover and interact with devices that are capable of providing PLI to an aggregation point without requiring the person installing theaggregation point120 to have knowledge of the devices that are on theIP network118. Thus, the physical-layer information resources described here can be easily integrated into theIP network118.
• TheIP network118 can include one or more local area networks and/or wide area networks (including for example the Internet). As a result, theaggregation point120,NMS130, andcomputer136 need not be located at the same site as each other or at the same site as theconnector assemblies102 or theinter-networking devices138.
• Various conventional IP networking techniques can be used in deploying thesystem100 ofFIG. 1. For example, conventional security protocols can be used to secure communications if they are communicated over a public or otherwise unsecure communication channel (such as the Internet or over a wireless communication link).
• In one implementation of the embodiment shown inFIG. 1, eachconnector assembly102, eachport104 of eachconnector assembly102, and each media segment is individually addressable. Where IP addresses are used to individually address eachconnector assembly102, a virtual private network (VPN) dedicated for use with thevarious connector assemblies102 can be used to segregate the IP addresses used for theconnector assemblies102 from the main IP address space that is used in theIP network118.
• Also, power can be supplied to theconnector assemblies102 using conventional “Power over Ethernet” techniques specified in the IEEE 802.3af standard, which is hereby incorporated herein by reference. In such an implementation, apower hub142 or other power supplying device (located near or incorporated into an inter-networking device that is coupled to each connector assembly102) injects DC power onto one or more of the wires (also referred to here as the “power wires”) included in the copper twisted-pair cable used to connect eachconnector assembly102 to the associated inter-networking device. Theinterface116 in theconnector assembly102 picks the injected DC power off of the power wires and uses the picked-off power to power the active components of thatconnector assembly102. In the second and third connector assembly configurations112 and114, some of theconnector assemblies102 are not directly connected to theIP network118 and, therefore, are unable to receive power directly from the power wires. Theseconnector assemblies102 receive power from theconnector assemblies102 that are directly connected to theIP network118 via the local connections that communicativelysuch connector assemblies102 to one another. In the fourth configuration115, theinterface116 picks the injected DC power off of the power wires and supplies power to themaster processor117 and each of theslave processors106 over the backplane.
• In the particular embodiment shown inFIG. 1, thesystem100 also supports conventional physical layer management (PLM) operations such as the tracking of moves, adds, and changes of the segments of physical media that are attached to theports104 of theconnector assemblies102 and providing assistance with carrying out moves, adds, and changes. PLI provided by theaggregation point120 can be used to improve upon conventional “guided MAC” processes. For example, information about the location of theport104 and the visual appearance (for example, the color or shape) of the relevant physical media segment (or connector attached thereto) can be communicated to a technician to assist the technician in carrying out a move, add, or change. This information can be communicated to a computer or smartphone used by the technician. Moreover, the PLI functionality that resides in thesystem100 can also be used to verify that a particular MAC was properly carried out by checking that the expected physical media segment is located in the expectedport104. If that is not the case, an alert can be sent to the technician so that the technician can correct the issue.
• The PLM functionality included in thesystem100 can also support conventional techniques for guiding the technician in carrying out a MAC (for example, by illuminating one or more light emitting diodes (LEDs) to direct a technician to aparticular connector assembly102 and/or to aparticular port104 or by displaying messages on a liquid crystal display (LCD) included on or near theconnector assemblies102.
• Other PLM functions include keeping historical logs about the media connected to the connector assembly. In the embodiment shown inFIG. 1, theaggregation point120 includes PLM functionality144 that implements such PLM functions. The PLM functionality144 does this using the physical layer information that is maintained at theaggregation point120.
• TheIP network118 is typically implemented using one or more inter-networking devices. As noted above, an inter-networking device is a type of connector assembly (and a particular implementation of aninter-networking device138 is referenced separately inFIG. 1 for ease of explanation only). Generally, an inter-networking device can be configured to read media information that is stored in or on the segments of physical media that are attached to its ports and to communicate the media information it reads from the attached segments of media (as well as information about the inter-networking device itself) to anaggregation point120 like any other connector assembly described here.
• In addition toconnector assemblies102, the techniques described here for reading media information stored in or on a segment of physical communication media can be used in one or more end nodes of the network. For example, computers (such as, laptops, servers, desktop computers, or special-purpose computing devices such as IP telephones, IP multi-media appliances, and storage devices) can be configured to read media information that is stored in or on the segments of physical communication media that are attached to their ports and to communicate the media information the read from the attached segments of media (as well as information about the devices themselves) to anaggregation point120 as described here.
• FIG. 2 is a block diagram of one high-level embodiment of aport104 andmedia reading interface106 that are suitable for use in thesystem100 ofFIG. 1.
• Eachport104 comprises afirst attachment point206 and asecond attachment point208. Thefirst attachment point206 is used to attach a first segment ofphysical communication media210 to theport104, and thesecond attachment point208 is used to attach a second segment ofphysical communication media212 to theport104.
• In the particular embodiment shown inFIG. 2, thefirst attachment point206 is located near the rear of the connector assembly. As a consequence, thefirst attachment point206 and the first segment ofphysical media210 attached thereto are also referred to here as the “rear attachment point”206 and the “rear media segment”210, respectively. Also, in this embodiment, therear attachment point206 is configured to attach therear media segment210 to theport104 in a semi-permanent manner. As used herein, a semi-permanent attachment is one that is designed to be changed relatively infrequently, if ever. This is also referred to sometimes as a “one-time” connection. Examples of suitablerear connectors206 include punch-down blocks (in the case of copper physical media) and fiber adapters, fiber splice points, and fiber termination points (in the case of optical physical media).
• In the embodiment shown inFIG. 2, thesecond attachment point208 is located near the front of theconnector assembly102. As a consequence, thesecond attachment point208 and the second segment ofphysical media212 are also referred to here as the “front attachment point”208 and the “front media segment”212, respectively. In the embodiment shown inFIG. 2, thefront attachment point208 for eachport104 is designed for use with “connectorized”front media segments212 that have identifier and attribute information stored in or on them. As used herein, a “connectorized” media segment is a segment of physical communication media that includes aconnector214 at at least one end of the segment. Thefront attachment point208 is implemented using a suitable connector or adapter that mates with the correspondingconnector214 on the end of thefront media segment212. Theconnector214 is used to facilitate the easy and repeated attachment and unattachment of thefront media segment212 to theport104. Examples of connectorized media segments include CAT-5, 6, and 7 twisted-pair cables having modular connectors or plugs attached to both ends (in which case, the front connectors are implemented using compatible modular jacks) or optical cables having SC, LC, FC, LX.5, MTP, or MPO connectors (in which case, the front connectors are implemented using compatible SC, LC, FC, LX.5, MTP, or MPO connectors or adapters). The techniques described here can be used with other types of connectors including, for example, BNC connectors, F connectors, DSX jacks and plugs, bantam jacks and plugs, and MPO and MTP multi-fiber connectors and adapters.
• Eachport104 communicatively couples the respectiverear attachment point206 to the respectivefront attachment point208. As a result, arear media segment210 attached to the respectiverear attachment point206 is communicatively coupled to anyfront media segment212 attached to the respectivefront attachment point208. In one implementation, eachport104 is designed for use with arear media segment210 and afront media segment212 that comprise the same type of physical communication media, in which case eachport104 communicatively couples anyrear media segment210 attached to the respectiverear attachment point206 to anyfront media segment212 attached to the respectivefront attachment point208 at the physical layer level without any media conversion. In other implementations, eachport104 communicatively couples anyrear media segment210 attached to the respectiverear attachment point206 to anyfront media segment212 attached to the respectivefront attachment point208 in other ways (for example, using a media converter if therear media segment210 and thefront media segment212 comprise different types of physical communication media).
• As shown inFIG. 2, theport104 is configured for use withfront media segments212 that include astorage device216 in which the media information for thatmedia segment212 is stored. Thestorage device216 includes a storage device interface that, when thecorresponding connector214 is inserted into (or otherwise attached to) afront attachment point208 of theport104, communicatively couples thestorage device216 to a correspondingmedia reading interface108 so that the associatedprogrammable processor106 can read the information stored in thestorage device216. In one implementation of the embodiment shown inFIG. 2, eachconnector214 itself houses thestorage device216. In another implementation of such an embodiment, thestorage device216 is housed within a housing that is separate from theconnector214. In such an implementation, the housing is configured so that it can be snapped onto themedia segment212 or theconnector214, with the storage device interface positioned relative to theconnector214 so that the storage device interface will properly mate with themedia reading interface108 when theconnector214 is inserted into (or otherwise attached to) thefront attachment point208.
• In some implementations, at least some of the information stored in thestorage device216 can be updated in the field (for example, by having an associatedprogrammable processor106 cause additional information to be written to thestorage device216 or changing or deleting information that was previously stored in the storage device216). For example, in some implementations, some of the information stored in thestorage device216 cannot be changed in the field (for example, identifier information or manufacturing information) while some of the other information stored in thestorage device216 can be changed in the field (for example, testing, media quality, or performance information). In other implementations, none of the information stored in thestorage device216 can be updated in the field.
• Also, thestorage device216 may also include a processor or micro-controller, in addition to storage for the media information. In which case, the micro-controller included in thestorage device216 can be used to execute software or firmware that, for example, controls one or more LEDs attached to thestorage device216. In another example, the micro-controller executes software or firmware that performs an integrity test on the front media segment212 (for example, by performing a capacitance or impedance test on the sheathing or insulator that surrounds the front physicalcommunication media segment212, (which may include a metallic foil or metallic filler for such purposes)). In the event that a problem with the integrity of thefront media segment212 is detected, the micro-controller can communicate that fact to theprogrammable processor106 associated with theport104 using the storage device interface (for example, by raising an interrupt). The micro-controller can also be used for other functions.
• FIG. 3 illustrates one embodiment of asystem300 that includes physical layer information (PLI) functionality as well as physical layer management (PLM) functionality. Thesystem300 comprises a plurality ofpatch panels302 that are housed within acommon chassis301. For example, in one common configuration, thechassis301 is installed in a communications closet or room and is mounted in a rack. In some larger installations, there are several racks ofchassis301 and patch panels302 (arranged, for example, in several bays). Thepatch panels302 can be packaged as blades that are slid into thechassis301.
• Eachpatch panel302 comprises a set of ports304 (for example, 16, 32, 48, or 512 ports304). The number ofports304 can vary frompatch panel302 topatch panel302.
• Each of theports304 is implemented as shown inFIG. 2. In general, in the context of the embodiment shown inFIG. 3, eachfront media segment312 comprises a “patch cord”312 that is used to selectively cross-connect twoports304 from the same ordifferent patch panels302. In this embodiment, eachpatch cord312 has amodular plug314 attached to each end that can be inserted into a front media connector of one of theports304 of thepatch panels302.
• In this way, respective rear media segments (not shown inFIG. 3) coupled to the twocross-connected ports304 can be communicatively coupled to one another in order to implement a logical communication link between the equipment that is coupled to the respective rear media segments. For example, in one exemplary application, a wall-mounted jack is communicatively coupled to a rear connector of aport304 using a suitable rear media segment such as a copper or fiber cable. The cable is typically routed through a building (for example, over, under, around, and/or through walls, ceilings, floors, and the like) and is not easily or frequently moved. If a first piece of equipment that is connected to one such wall-mounted jack needs to be communicatively coupled to a second piece of equipment that is connected to another such wall-mounted jack, apatch cord312 can be used to establish the connection.
• As shown inFIG. 3, a master processor unit (MPU)330 is also housed within thechassis301. The master processor unit (MPU)330 communicates withslave processor modules318 included in each of thepatch panels304 over abackplane315.FIG. 4 is a block diagram of one embodiment of eachslave processor module318 shown inFIG. 3. Eachslave processor module318 comprises a slaveprogrammable processor320 that executessoftware322. The execution of thesoftware322 causes theslave processor320 to carry out various functions described below. Eachslave processor module318 also includesmemory324 that is coupled to theslave processor320 for storing program instructions and data. Theslave processor320 in eachslave processor module318 is coupled to thebackplane315 using a suitable interface.
• Thesystem300 is designed to be used with patch cords312 (or other front media segments) that have identifier and attribute information of the type described above in connection withFIG. 2 stored in or on them. Each of theports304 of eachpatch panel302 comprises a respective media reading interface (not shown inFIG. 3). The slaveprogrammable processor320 in eachpatch panel302 is communicatively coupled to each of the media reading interfaces in thatpatch panel302 using a bus or other interconnect (not shown). The slaveprogrammable processor320 is configured to determine if the state of aport304 changes. The state of aport304 changes, for example, when a patch cord is inserted into a previously empty front connector or when apatch cord312 is removed from a front connector, or when a different patch cord is inserted into a previously occupied front connector.
• In one implementation of such an embodiment, each media reading interface is configured so that the slaveprogrammable processor320 can detect changes in the state of eachport304. For example, the electrical contact structure of the media reading interface can be configured so that an electrical signal changes state when a patch cord is inserted into or removed from a port304 (for example, by closing or opening an electrical circuit). Theslave processor320 detects such state changes to detect when a patch cord has been inserted into or removed from the front connector of eachport304. Examples of such contact structures are U.S. Provisional Patent Application Ser. No. 61/252,395, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS AND METHODS THEREOF” (also referred to here as the “'395 Application”), U.S. Provisional Patent Application Ser. No. 61/253,208, filed on Oct. 20, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY SYSTEMS” (also referred to here as the “'208 Application”), and U.S. Provisional Patent Application Ser. No. 61/252,964, filed on Oct. 19, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY SYSTEMS” (also referred to here as the “'964 Application”). The '395 Application, the '208 Application, and the '964 Application are hereby incorporated herein by reference.
• Alternatively, theslave processor320 can be configured to periodically scan all of the media reading interfaces included in thatpatch panel302 to determine if the state of any of the associatedports304 has changed.
• Also, when thesoftware322 executing on the slaveprogrammable processor320 in eachpatch panel302 determines that a patch cord has been inserted into a previously empty front connector or that a different patch cord has been inserted into a previously connected front connector, thesoftware322 reads the information stored in or on the inserted patch cord.
• Any changes in the state of thepatch panel ports304 and the information that is read from the patch cords are communicated to theMPU330 over thebackplane315. The port state information and the information read from the patch cords are collectively referred to here as “port information.”
• Thesoftware322 executing on the slaveprogrammable processor320 in eachpatch panel302 also communicates information about therespective patch panel302 to theMPU330 over the backplane115 (such information is also referred to here as “patch panel information”). Thepatch panel software322 communicates the patch panel information to theMPU330, for example, in the following situations: in response to a request from theMPU330, or when thepatch panel302 first powers up, or when any of patch panel's information changes, or after a predetermined amount of time has elapsed since last communicating the patch panel information to theMPU330.
• As shown inFIG. 3, each of theports304 of eachpatch panel302 includes a respective visual indicator316 (such as a light emitting diode (LED)) that is coupled to the slaveprogrammable processor318 over an internal bus or other interconnect (not shown). Thevisual indicator316 is located near theport304 with which thevisual indicator316 is associated. The slaveprogrammable processor332 can actuate each of the visual indicators316 (for example, by illuminating an LED) in order to identify the associatedport304.
• As shown inFIG. 3, theMPU330 is configured to communicate with and control theslave processor modules318. Also, theMPU330 is configured to communicate with other devices over an IP network350 (such as LAN352). More specifically, theMPU330 is configured to communicate with anaggregation point353 over theLAN352.FIG. 5 is a block diagram of one embodiment of themaster processor unit330 ofFIG. 3. TheMPU330 includes a masterprogrammable processor332 that executessoftware334. The execution of thesoftware334 causes the masterprogrammable processor332 of theMPU330 to carry out various functions described below. TheMPU330 also includesmemory336 that is coupled to themaster processor332 for storing program instructions and data. Themaster processor332 is coupled to thebackplane315 of thechassis301. Theslave processor320 in each of thepatch panels302 communicates with the masterprogrammable processor332 in theMPU330 over thebackplane315. In the particular embodiment shown inFIG. 3, most of the processing that is performed in thesystem300 is performed by the masterprogrammable processor332 in theMPU330. As a result, a relatively low power slaveprogrammable processor318 can be used in each of thepatch panels302, such as an 8-bit or 16-bit microcontroller. The masterprogrammable processor332 in theMPU330, in such an embodiment, is implemented using a 16-bit or 32-bit microcontroller or microprocessor.
• TheMPU330 further comprises anETHERNET interface340 that is used to communicatively couple the MPU330 (and the masterprogrammable processor332 included therein) to one or more Internet Protocol (IP) networks350 (shown inFIG. 3). In the particular embodiment shown inFIG. 3, theETHERNET interface340 is coupled to a local area network (LAN)352. This connection to theLAN352 can be implemented, for example, by using a cable to connect theETHERNET interface340 of theMPU330 to oneport304 of a patch panel302 (by attaching the cable to the rear attachment point306 of that port304). Each of multiple ports of an inter-networking device (such as a hub, router, or switch) (not shown inFIG. 3) is also connected torespective ports304 of a patch panel302 (by connecting respective cables to the respective rear attachment points306 of the ports304). TheETHERNET interface340 of theMPU330 is cross-connected to a port of the inter-networking device by inserting oneend314 of apatch cord312 into the front connector308 of theport304 that is connected to theETHERNET interface340 and by inserting theother end314 of thepatch cord312 into the front connector308 of the port306 that is connected to one of the ports of the inter-networking device. The other ports of the inter-networking device are connected (via the patch panels302) to other items of end user equipment356 (shown inFIG. 3) (such as computers) and other inter-networking devices (such as gateways or network interface devices that connect theLAN352 to a wide area network such the Internet358 (shown inFIG. 3)).
• As shown inFIG. 5, in this particular embodiment, theMPU software334 includes a TCP/IP stack342 that enables theMPU processor332 to communicate with other devices over the one ormore IP networks350.
• In the embodiment shown inFIG. 3, power is supplied to theMPU330 and theslave processor modules318 over the twisted-pair copper wiring that is used to connect theMPU330 to theLAN352. Power is supplied using Power over Ethernet techniques specified in the IEEE 802.3af standard. In such an embodiment, the inter-working device to which theMPU330 is coupled includes apower hub354 or other power supplying device (located near or incorporated into it) that injects DC power onto one or more of the wires (also referred to here as the “power wires”) included in the copper twisted-pair cable used to connect theMPU330 to the inter-networking device. TheETHERNET interface340 inMPU330 picks the injected DC power off of the power wires and uses the picked-off power to power the active components in theMPU330. Also, power is supplied from theMPU330 to thepatch panels302 over thebackplane315 in order to power the active components in thepatch panels302.
• In the particular embodiment shown inFIG. 4, theMPU330 also comprises a power supply unit (PSU)344 for situations where the devices in thechassis301 are not powered using Power over Ethernet. ThePSU344 can be connected to one or more external power sources346 (shown inFIG. 3) (such as the alternating current (AC) power grid and/or a telco/data center direct current (DC) power source) and converts the external power received from theexternal power source346 to power that is suitable for use by the active components of theMPU330 and thepatch panels302.
• TheMPU software334 executing on the MPUprogrammable processor332 receives the port and patch panel information from all of thepatch panels302 and maintains a data store362 (shown inFIG. 5) in which the information is stored and organized. TheMPU software334 executing on the MPUprogrammable processor332 is also configured to communicate with one or more aggregation points353. In the particular embodiment shown inFIG. 5, theMPU software334 includesdiscovery protocol software364 that is used by theMPU330 and theaggregation point353 to discover and connect with one another. TheMPU software334 also includescommunication protocol software366 that is used to communicate port and patch panel information (and other PLI) to and from theaggregation port353.
• TheMPU software334 also includes functionality that enables users, systems, and devices to directly interact with theMPU330 over the IP networks350. In the particular embodiment shown inFIGS. 3-11, theMPU software334 is configured to interact with users using a web browser. In this embodiment, theMPU software334 includes a web server370 (shown inFIG. 5) that enables theMPU330 to interact with a user's web browser over theIP networks350 using the HyperText Markup Language (HTML) protocol (and related protocols such as the Asynchronous JavaScript and XML (AJAX) protocols). In the particular embodiment shown inFIGS. 3-11, theMPU software334 is also configured to directly interact with users, systems, and devices in other ways. For example, theMPU software334 includesTELNET software372 that enables other users, systems, and devices to telnet into theMPU330 and an email server374 (implementing, for example, the Simple Mail Transfer Protocol (SMTP)) that enables theMPU software334 to send email messages to other users, systems, and devices. TheMPU software334 also includes security andencryption software376 to enable theMPU software334 to communicate in a secure manner (for example, using Secure Sockets Layer (SSL) sessions or virtual private networks (VPNs)).
• In the embodiment shown inFIGS. 3-11, thesystem300 is configured to have a user manually enter, for eachport304 that has a respective rear media segment310 attached to its rear attachment point, information about the physical media that is used to implement that rear media segment. In this embodiment, the rear media segments are connected to the rear attachment points in a semi-permanent manner, and typically these connections do not change often, if ever. As a result, information about the physical media used to implement the rear media segments can be manually entered and verified in connection with the initial installation of the media and will typically remain valid thereafter. This information can include information similar to the port information stored in or on a patch cord and is also referred to here as “rear media information.” In the event that a change is made to the media that is attached to a rear attachment point of aport304, the corresponding physical media information for thatport304 would need to be manually updated. This read media information, for example, can be entered into a spreadsheet or other file. The spreadsheet is then uploaded to theaggregation point353. Theaggregation point353 associates the read media information included in the spreadsheet with information about thepatch panels302 and theports304 that it obtains from theMPU330.
• Also, when an inter-networking device (such as a switch or router) is connected to the rear attachment points of theports304 of apatch panel302, information about the inter-networking device (such as the device's MAC address and an assigned IP address) and information indicating which port of the inter-networking device is connected to whichport304 of thepatch panel302 can be manually entered and provided to theaggregation point353 in connection with the initial installation of the inter-networking device. This information is also referred to here as “inter-networking device information.” Also, as noted above, if the inter-networking device includes PLI functionality, such inter-networking device information can be automatically captured by the inter-networking device and communicated to theaggregation point353.
• In addition, in the embodiment shown inFIGS. 3-11, thesystem300 is configured to have a user enter information about the layout of the building or buildings in which the network is deployed, as well as information indicating where eachpatch panel302, rear media segment, inter-networking device, and wall outlet is located within the building. This information is also referred to here as “location information”. For example, this location information can be entered into a spreadsheet and uploaded to theaggregation point353, which associates the location information with the other PLI it has obtained about thesystem300.
• In the embodiment shown inFIGS. 3-11, theaggregation point353 has access to many types of physical layer information including, for example, device information (that is, the port information, patch panel information, inter-networking device information and information any wall outlets and end user devices), media information (that is, front media information-including the media information stored on the patch cords—and rear media information), and location information.
• In the embodiment shown inFIG. 3, theMPU330 also includesadditional interfaces382 for communicatively coupling the MPU330 (and the MPU programmable processor332) to one or more external sensors (for example, external temperature sensors) and alarms384 (shown inFIG. 1). TheMPU330 can be communicatively coupled to such external sensors andalarms384 using wired and/or wireless communication links. In one application, a thermal map of the network can be produced from temperature readings, which may be useful for HVAC purposes.
• Also, as shown inFIG. 5, theMPU330 includes aninterface378 by which a technician can directly connect a device such as a computer, personal digital assistant (PDA), or smartphone to theMPU330 and interact with thesoftware334 executing themaster processor332.
• In one implementation of the embodiment shown inFIGS. 3-11, theMPU330 and theslave processor module318, media reading interfaces and associatedvisual indicators316 are integrated into thepatch panel302 along with the other components. In another implementation, theMPU330 and theslave processor module318, media reading interfaces and associatedvisual indicators316 are housed within one or more modules that are separate from therespective patch panel302. In such an implementation, the separate modules are attached to the front of therespective patch panel302 so that eachvisual indicator316 and media reading interface is positioned near its correspondingport304.
• In some embodiments, a display (such as a liquid crystal display) is incorporated into theMPU330, theslave processor modules318, or thepatch panel302 to display messages at thepatch panel302. Also, in some embodiments, a user input mechanism (such as one or more buttons) is incorporated into theMPU330, theslave processor modules318, or thepatch panel302 to receive input from a user that is located near thepatch panels302.
• FIG. 6 is a diagram illustrating one embodiment of apatch cord312 that is suitable for use in thesystem300 ofFIG. 3. Thepatch cord312 shown inFIG. 6 is suitable for use with an implementation of thepatch panel302 ofFIG. 3 where the front connectors of theports304 are implemented using modular RJ-45 jacks. Thepatch cord312 shown inFIG. 6 comprises a copper unshielded twisted-pair (UTP)cable386. TheUTP cable386 includes eight conductors arranged in four conductor pairs. Thepatch cord312 also comprises two RJ-45plugs314, one at each end of the cable386 (only one of which is shown inFIG. 6). The RJ-45plugs314 are designed to be inserted into the RJ-45 modular jacks used as the front connectors. Each RJ-45plug314 comprises acontact portion388 in which eight, generally parallelelectrical contacts390 are positioned. Each of the eightelectrical contacts390 are electrically connected to one of the eight conductors in theUTP cable386.
• Eachplug314 also comprises (or is attached to) a storage device392 (for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device). The media information described above for thepatch cord312 is stored in thestorage device392. Thestorage device392 includes sufficient storage capacity to store such information. Eachstorage device392 also includes astorage device interface394 that, when thecorresponding plug314 is inserted into a front connector of aport304, communicatively couples thestorage device392 to the corresponding media reading interface so that theprogrammable processor320 in thecorresponding patch panel302 can read the information stored in thestorage device392.
• Examples of such apatch cord312 and plug314 are described in the '395 Application, the '208 Application, and the '964 Application.
• The embodiment shown inFIGS. 3-11 is generally described here as being implemented using thepatch cord312 shown inFIG. 6. However, other types of patch cords can be used, one of which is shown inFIG. 7.
• FIG. 7 is a diagram illustrating another embodiment of apatch cord312′ that is suitable for use in thesystem300 ofFIG. 3. Thepatch cord312′ shown inFIG. 7 is suitable for use with an implementation of thepatch panel302 ofFIG. 3 where the front connectors of theports304 are implemented using fiber LC adapters or connectors. Thepatch cord312′ shown inFIG. 7 comprises anoptical cable386′. Theoptical cable386′ includes an optical fiber enclosed within a suitable sheathing. Thepatch cord312′ also comprises twoLC connectors314′, on at each of thecable386′. EachLC connector314′ is designed to be inserted into an LC adapter used as the front connector of aport304. EachLC connector314′ comprises anend portion388′ at which an optical connection with the optical fiber in thecable386′ can be established when theLC connector314′ is inserted in an LC adapter of aport304.
• EachLC connector314′ also comprises (or is attached to) astorage device392′ (for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device). The media information described above for thepatch cord312 is stored in thestorage device392′. Thestorage device392′ includes sufficient storage capacity to store such information. Eachstorage device392′ also includes astorage device interface394′ that, when thecorresponding LC connector314′ is inserted into a front connector of aport304, communicatively couples thestorage device392′ to the corresponding media reading interface so that the slaveprogrammable processor320 in thecorresponding patch panel302 can read the information stored in thestorage device392′.
• In some implementations of thepatch cords312 and312′, thestorage devices392 and392′ are implemented using a surface-mount EEPROM or other non-volatile memory device. In such implementations, the storage device interfaces and media reading interfaces each comprise four leads—a power lead, a ground lead, a data lead, and an extra lead that is reserved for future use. The four leads of the storage device interfaces come into electrical contact with four corresponding leads of the media reading interface when the corresponding plug or connector is inserted in the corresponding front connector of aport304. Each storage device interface and media reading interface are arranged and configured so that they do not interfere with data communicated over the patch cord. In other embodiments, other types of interfaces are used. For example, in one such alternative embodiment, a two-line interface is used with a simple charge pump. In other embodiments, additional lines are provided (for example, for potential future applications).
• Examples of suchfiber patch cords312′ andconnectors314′ are described in U.S. Provisional Patent Application Ser. No. 61/252,386, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS AND METHODS THEREOF” (also referred to here as the “'386 Application”), U.S. Provisional Patent Application Ser. No. 61/303,961, filed on Feb. 12, 2010, titled “FIBER PLUGS AND ADAPTERS FOR MANAGED CONNECTIVITY” (the “'961 Application”), and U.S. Provisional Patent Application Ser. No. 61/303,948, filed on Feb. 12, 2010, titled “BLADED COMMUNICATIONS SYSTEM” (the “'948 Application”). The '386 Application, the '961 Application, and the '948 Application are hereby incorporated herein by reference.
• In some implementations of thepatch cords312 and312′, eachplug314 orconnector314′ itself houses the respective storage device and storage device interface. In implementations, each storage device and corresponding storage device interface are housed within a housing that is separate from the corresponding plug or connector. In such implementations, the housing is configured so that it can be snapped onto (or otherwise attached to) the cable or the plug or connector, with the storage device interface positioned relative to the plug or connector so that the storage device interface will properly mate with the relevant media reading interface when the plug or connector is inserted into the front connector of thecorresponding port304.
• A hand-held test set can be provided that includes a port into which theplug314 orconnector314′ of apatch cord312 or312′ can be inserted in order to read the media information stored in the storage device. The hand-held test set also includes a display of some type to display the media information that was read from the storage device.
• In other embodiments, the storage device also includes an optical or infrared interface for reading the media information stored in the storage device while thecorresponding patch cord312 or312′ is connected to one ormore patch panels302. This enables a technician to read the media information stored in the storage device without having to remove thepatch cord312 or312′ in order to use the hand-held tester described above.
• The remainder of the description of the embodiment shown inFIGS. 3-11 generally refers to thepatch cord312 shown inFIG. 6. However, it is to be understood that other patch cords can be used (such as thepatch cord312′ shown inFIG. 7).
• FIG. 8 is a block diagram of one embodiment of anaggregation point353. The particular embodiment of anaggregation point353 shown inFIG. 8 is described here as being implemented for use in thesystem300 ofFIG. 3, though other embodiments can be implemented in other ways.
• Theaggregation point353 is typically implemented assoftware800 that executes on a workstation orother computer802. Theworkstation802 comprises at least oneprogrammable processor804 on which thesoftware800 executes. Thesoftware800 comprises program instructions that are stored (or otherwise embodied) on an appropriate storage medium or media from which at least a portion of the program instructions are read by theprogrammable processor804 for execution thereby. Theworkstation802 also comprisesmemory806 for storing the program instructions and any related data during execution of thesoftware800.
• Theworkstation802 on which theaggregation point software800 executes also includes one ormore interfaces808 that communicatively couple theaggregation point353 to devices or entities with which it communicates. More specifically, the one ormore interfaces808 communicatively couple theaggregation point353 to these devices or entities over the one ormore IP networks350. In one implementation of such an embodiment, at least one of theinterfaces808 comprises an ETHERNET network interface for coupling theaggregation point353 to the one ormore IP networks350.
• Theaggregation point software800 comprisesPLI aggregation software810 that enables theaggregation point353 to automatically discover and connect with devices that are able provide PLI and other information to the aggregation point353 (such as the patch panels302). Theaggregation point353 and thePLI aggregation software810 can be used to receive physical layer information from various types of connector assemblies that have functionality for automatically reading information stored in or on a segment of physical communication media. Examples of such devices are noted above and include, for example,patch panels302 and inter-networking devices. Also, theaggregation point353 andPLI aggregation software810 can also be used to receive physical layer information from other types of devices that have functionality for automatically reading information stored in or on the segment of physical communication media. Examples of such devices include end-user devices—such as computers, peripherals (for example, printers, copiers, storage devices, and scanners), and IP telephones—that include functionality for automatically reading information stored in or on the segment of physical communication media.
• In the particular embodiment shown inFIG. 8, thePLI aggregation software810 comprisessoftware812 that uses one or more discovery protocols to discover and connect with devices that are able to provide PLI information to the aggregation point353 (assuming those devices also support those discovery protocols). Examples of discovery protocols include, without limitation, Multicast DNS (mDNS), DNS based Service Discovery (DNS-SD), Universal Plug and Play (UPnP), Simple Device Discovery Protocol (SDDP), and Service Location Protocol (SLP) as well as proprietary protocols, and extensions of other protocols (such as Dynamic Host Configuration Protocol (DHCP)). In this embodiment, when a patch panel302 (or other device that is able to provide PLI information to the aggregation point353) is first coupled to theLAN352, theMPU330 of thepatch panel302 first obtains an IP address (typically from a DHCP server for the LAN352). TheMPU330 in thepatch panel302 then uses the discovery protocol to broadcast an informational message to the other nodes on theLAN353. The informational message includes information about the services that thepatch panel302 provides, which in this case includes services related to providing PLI information for thepatch panel302 andpatch cords312 coupled to thepatch panels302. Theaggregation point353 listens for such informational messages. When theaggregation point353 receives an informational message from apatch panel302 that it can manage, theaggregation point353 uses the discovery protocols to send a corresponding message to the patch panel302 (using the address information included in the received informational message) requesting more information about thepatch panel302. In response to this request,MPU330 in thepatch panel302 provides the requested information. At this point, theaggregation point353 is able to control and receive notifications from theMPU330 in thepatch panel302. Similar processing can be performed when other devices that provide PLI to an aggregation point353 (such as the inter-network device) join theLAN352.
• Likewise, when anaggregation point353 is connected to theLAN352, thediscovery protocol software812 uses the discovery protocols to broadcast an informational message to all the nodes on theLAN352. This message indicates that theaggregation point353 is searching for devices and/or services that include the PLI functionality described here. Devices that are able to provide PLI to an aggregation point (devices such aspatch panels320 and inter-network devices) listen for such messages. If those devices meet the search criteria set forth in the message, the devices respond with an appropriate message advertising the services they provide. When theaggregation point353 receives such a message from a device that it can manage, thesoftware812 sends a message to that device (using the address information included in the received message) requesting more information about that device. In response to this request, the device provides the requested information to theaggregation point353. At this point, theaggregation point353 is able to control and receive notifications from the device.
• In this way, when devices that are able to provide PLI to an aggregation point are coupled to theLAN352, the aggregation points353 is able to automatically discover the device and start aggregating physical layer information for that device without requiring a technician installing the device to know about the aggregation points that are on theLAN352. Similarly, when theaggregation point353 is coupled to theLAN352, theaggregation point353 is able to automatically discover and interact with devices that are capable of providing PLI to theaggregation point353 without requiring the technician installing theaggregation point353 to know about such devices that are on theLAN352. Thus, the physical-layer information resources described here can be easily integrated into theLAN352.
• In the embodiment shown inFIG. 8, thePLI aggregation software810 also includessoftware814 that is configured to obtain physical layer information from the devices it has discovered and connected to using the discovery protocol software812 (for example, devices such as thepatch panels302 and inter-network devices). Adatabase manager816 is used to store the PLI information that theaggregation software810 obtains in a database. In the particular embodiment shown inFIG. 8, thesoftware814 uses one or more appropriate protocols to communicate physical layer information to and from such devices. Examples of protocols that can be used include, without limitation, the File Transfer Protocol (FTP), the Trivial File Transfer Protocol (TFTP), the Hypertext Transfer Protocol (HTTP), the Simple Network Management Protocol (SNMP), the Common Gateway Interface (CGI) protocol, the Representational State Transfer (REST) protocol, and the Simple Object Access Protocol (SOAP). The devices that theaggregation point353 receives information from also implement at least some of the protocols implemented by theaggregation point353 to organize, track, store, and communicate physical layer information.
• Theaggregation point353 andaggregation software810 can also be used to obtain other types of physical layer information. For example, in this embodiment, theaggregation software810 also obtains information about physical communication media segments that is not otherwise automatically communicated to an aggregation point. One example of such information is information about non-connectorized cables that do not otherwise have information stored in or on them that are attached to a patch panel302 (including, for example, information indicating which ports of thepatch panel302 are connected to which ports of other devices in thenetwork350 by that cable as well as media information about the cable).
• Another example of such information is information about patch cords that are connected to devices that are not be able to read media information that is stored in or on the patch cords that are attached to their ports and/or that are not able to communicate such information to the aggregation point353 (for example, because such devices do not include such functionality, because such devices are used with patch cords that do not have media information stored in or on them, and/or because bandwidth is not available for communicating such information to the aggregation point353). In this example, this information can include, for example, information about the devices themselves (such as the devices' MAC addresses and IP addresses if assigned to such devices), information indicating which ports of the devices are connected to which ports of other devices in the network, and information about the physical media attached to the ports of the devices. This information can be provided to theaggregation point353, for example, by manually entering such information into a file (such as a spreadsheet) and then uploading the file to theaggregation point353 in connection with the initial installation of each of the various items. Such information can also, for example, be directly entered using a user interface provided by the aggregation point353 (for example, using a web browser). In the embodiment shown inFIG. 8, theaggregation point software810 includes aweb server818 to facilitate the upload of files and/or the direct entry of such manually entered information.
• Theaggregation software810 can also obtain information about the layout of the building or buildings in which thenetwork350 is deployed, as well as information indicating where eachpatch panel302 device, patch cord (or other item of physical communication media), and inter-networking device is located within the building. This information can be, for example, manually entered and uploaded to theaggregation point353 in connection with the initial installation of each of the various items. In one implementation, such location information includes an X, Y, and Z location for each port or other termination point for each physical communication media segment that is terminated in the network350 (for example, X, Y, and Z location information of the type specified in ANSI/TIA/EIA 606-A Standard—Administration Standard For The Commercial Telecommunications Infrastructure).
• Theaggregation software810 can also obtain and maintain testing, media quality, or performance information relating to the various items of physical communication media that exist in the network. The testing, media quality, or performance information, for example, can be results of testing that is performed when a particular segment of media is manufactured and/or when testing is performed when a particular segment of media is installed or otherwise checked.
• Theaggregation software810 also provides an interface for external devices or entities to access the physical layer information maintained by theaggregation point353. This access can include retrieving information from theaggregation point353 as well as supplying information to theaggregation point353. In this embodiment, theaggregation point353 is implemented as “middleware” that is able to provide such external devices and entities with transparent and convenient access to the PLI maintained by theaccess point353. Because theaggregation point353 aggregates PLI from the relevant devices on theIP network350 and provides external devices and entities with access to such PLI, the external devices and entities do not need to individually interact with all of the devices in theIP network350 that provide PLI, nor do such devices need to have the capacity to respond to requests from such external devices and entities.
• Theaggregation point software810, in the embodiment shown inFIG. 8, implements an application programming interface (API)820 by which application-layer functionality in such other devices can gain access to the physical layer information maintained by theaggregation point353 using a software development kit (SDK) that describes and documents theAPI820. In one implementation of such an embodiment, theAPI820 is configured to use the Simple Object Access Protocol (SOAP) protocol for communications between theaggregation point353 and such external devices or entities. In other implementations, other protocols can be used (for example, the SNMP or CGI protocols).
• For example, an application370 (shown inFIG. 3) executing on acomputer356 can use theAPI820 provided by theaggregation point353 to access the PLI information maintained by the aggregation point353 (for example, to retrieve such information from theaggregation point353 and/or to supply information to the aggregation point353). Thecomputer356 is coupled to theLAN352 and accesses theaggregation point353 over theLAN352.
• FIG. 9 is a block diagram of one embodiment of a network management system (NMS)380 that is specially configured to use the physical layer information that is made available by thesystem300 ofFIG. 3. The particular embodiment of anNMS380 shown inFIG. 9 is described here as being implemented for use in thesystem300 ofFIG. 3, though other embodiments can be implemented in other ways.
• TheNMS380 is typically implemented assoftware900 that executes on a workstation orother computer902. Theworkstation902 comprises at least oneprogrammable processor904 on which thesoftware900 executes. Thesoftware900 comprises program instructions that are stored (or otherwise embodied) on an appropriate storage medium or media from which at least a portion of the program instructions are read by theprogrammable processor904 for execution thereby. Theworkstation902 also comprisesmemory906 for storing the program instructions and any related data during execution of thesoftware900.
• Theworkstation902 on which theNMS software900 executes also includes one ormore interfaces908 that communicatively couple theNMS380 to the network elements that theNMS380 manages and otherwise interacts with. More specifically, the one ormore interfaces908 communicatively couple theNMS380 to these network elements over the one ormore IP networks350. In one implementation of such an embodiment, at least one of theinterfaces908 comprises an ETHERNET network interface for coupling theNMS380 to the one ormore IP networks350.
• TheNMS software900 comprisesnetwork management functionality910 that implements various conventional NMS functions, such as displaying status and alarm information about the various elements in the managed network. In the particular embodiment described here, theNMS functionality910 includes functionality for displaying a user interface for theNMS380 and data management functionality for organizing, tracking and storing the information it receives from the managed network elements.
• TheNMS software900 also includes physical layer information (PLI)functionality914. ThePLI functionality914 is configured to retrieve physical layer information from theaggregation point353 and provide it to theNMS functionality910 for use thereby. TheNMS functionality910 uses the retrieved physical layer information to perform one or more network management functions. In the embodiment shown inFIG. 9, thePLI functionality914 retrieves physical layer information from theaggregation point353 using the API820 (shown inFIG. 8) implemented by theaggregation point353. To do this, thePLI functionality914 supports the protocol used by theAPI820. TheNMS software900 communicates with theaggregation point353 over the IP networks350. Theaggregation point software800 executing on theaggregation point353 processes and responds to API calls from theNMS380.
• The retrieved physical layer information can be used by theNMS380 to provide Layer 1 (of the OSI model) resolution in the information it displays. For example, in one implementation of the embodiment shown inFIG. 9, theNMS software900 displays a graphical representation of the managed network that shows the logical communication links between various network elements. When a user clicks on one of the logical communication links, theNMS software900 uses thePLI functionality914 to display the various physical layer items (for example, physical communication media, patch panels, and wall outlets) that implement that logical communication link, as well as information about those physical layer items (for example, their location, product name, type, color, length, temperature, etc.) that was retrieved from theaggregation point353.
• In the particular embodiment shown inFIG. 9, theNMS software900 also includes physicallayer management functionality912 that uses the physical layer information received from theaggregation point353 to carry out various PLM functions. For example, thePLM functionality912 enables theNMS380 to manage patch cord moves, adds, or changes (MAC) for thepatch panels302. This can be done by having thePLM functionality912 communicate information about the MAC to a computer or other device used by the technician using thenetwork350. This information can include physical layer information received from an aggregation point353 (for example, information identifyingparticular ports304,patch panels302, andpatch cords312 involved in the MAC and the locations thereof as well as information about the visual attributes of the items involved in the MAC). Also, thePLM functionality912 enables theNMS380 to receive alarms and warning messages from theaggregation point353 that are related to moves, adds, or changes (for example, when an unrequested move, add, or change has been made or where a requested move, add, or change was made incorrectly). In other words, thePLM functionality912 in theNMS380 can be used to verify that a particular requested MAC was properly implemented and, if it was not, inform the technician of that fact. In addition, thePLM functionality912 in theNMS380 can be configured to perform a “guided” MAC in which thePLM functionality912 causesappropriate LEDS316 on thepatch panels302 to be illuminated or flashed in order to help the technician identify theports304 involved in a MAC. ThePLM functionality912 can do this by using an appropriate API call to request that theLEDs316 be illuminated. Theaggregation point353, in response to such an API call, sends a request to theappropriate MPU330 to have the appropriateslave processor modules318 cause theLEDs316 to be illuminated.
• This MAC functionality can be implemented as a standalone application that is not a part of aNMS380.
• Other examples of functions that theNMS380 can perform using the physical layer information include raising an alarm or warning if a predetermined specific patch cord (or a particular type of patch cord) is not used to implement a particular cross connection, enforcing other policies, and/or using the location information included in the physical layer information to assist in E911 or location based services (LBS) processing that theNMS380 supports (for example, to determine where an IP phone is located).
• Another example of PLI-enabled functionality that can be added to anNMS380 is shown inFIG. 10.FIG. 10 is a flow diagram of one exemplary embodiment of a method of compliance tracking in a network that includes the PLI functionality described here. The particular exemplary embodiment ofmethod1000 shown inFIG. 10 is described here as being implemented as a part of thePLI functionality914 of theNMS380 shown inFIG. 9 for use in thesystem300 shown inFIG. 3 (though other embodiments can be implemented in other ways).
• In such an exemplary embodiment, the physical layer information that is tracked and aggregated at theaggregation point353 includes information about the compliance of various parts of thesystem300 with various standards. Standards such as the TIA/EIA-568-B family of standards define performance requirements for various physical layer cabling components that are used to implement networks, performance requirements for “permanent links” included within a give channel, and performance requirements for the overall channel.
• For each channel that is being installed, information about the compliance of eachpatch cord312 and plug314 used in the channel with the requirements of the relevant standards is stored in the relevant non-volatile memory392 (block1002). This information can be determined by tests performed by the manufacture and/or an installer. This information can include an indication of whether or not each component associated with thatpatch cord312 complies with the relevant performance specifications as well as the underlying performance information that was used to determine compliance. In other words, the performance margin or envelope for each such component can be stored in therelevant EEPROM392. This component compliance data is automatically read when thepatch cord312 is connected to aport304 of thepatch panel302 and communicated to the relevant aggregation point352 (block1004).
• When a particular permanent link is installed (for example, a link between a wall outlet and a punch down block of a patch panel302), the installer tests the performance of the permanent link and certifies its compliance with the requirements of the relevant standards (block1006). Information about the compliance of the permanent link with the requirements of the relevant standards is communicated to the aggregation point353 (for example, by uploading such information as described above) (block1008). This information can include an indication of whether or not the permanent link complies with the relevant performance requirements as well as the underlying performance information that was used to determine compliance. In other words, the performance margin or envelope for the permanent link can be provided to theaggregation point353 in addition to an indication of compliance.
• In the embodiment shown inFIG. 10, the installer also tests the overall channel and certifies the compliance of the overall channel with the requirements of the relevant standards (block1010). Information related to the compliance of the overall channel is communicated to the aggregation point353 (for example, by uploading such information as described above). Theaggregation point353 then identifies the particular components that were used in the channel when the channel was certified (block1012). For example, theaggregation point353 knows whichpatch cords312 andpatch panel ports304 were used in the channel when it was certified. If in the future one of thosepatch cords312 were to be replaced, theaggregation point353 is able to automatically determine that the original basis for the certification of channel compliance no longer exists (block1014). When such apatch cord312 is replaced, theaggregation point353 can also automatically determine if the overall channel likely remains compliant with the relevant standards by checking if the replacement path cord has been certified to meet the component specifications needed for channel compliance and verifying that the permalink link for the channel remains undisturbed and that the patch cord is connected to the same ports as before (block1016). Such information can be used in troubleshooting performance problems in the network.
• Method1000 is one example of how such compliance information can be used. Also, the embodiment ofmethod1000 shown inFIG. 10 is described here as being implemented in theNMS380 ofFIG. 8, though it is to be understood that similar functionality can be implemented in other parts of the system300 (for example, in theaggregation point353 or as a standalone application). Moreover, other types of compliance information can be received and stored by an aggregation point and used in compliance tracking. Examples of such compliance information include, without limitation, information about compliance with communications, regulatory, or military rules, regulations, laws, specifications, or standards.
• FIG. 11 is a block diagram of one embodiment of aninter-networking device354 that is specially configured to use the physical layer information that is made available by thesystem300 ofFIG. 3. The particular embodiment of aninter-networking device354 shown inFIG. 11 is described here as being implemented for use in thesystem300 ofFIG. 3, though other embodiments can be implemented in other ways.
• In the embodiment shown inFIG. 11, theinter-networking device354 comprises at least oneprogrammable processor1100 that executes software1102 (referred to as “firmware” in some embodiments) that causes theinter-networking device354 to carry out various functions described below. Thesoftware1102 comprises program instructions that are stored (or otherwise embodied) on an appropriate storage medium or media (for example, flash memory) from which at least a portion of the program instructions are read by theprogrammable processor1100 for execution thereby. Theinter-networking device354 also includesmemory1104 that is coupled to theprogrammable processor1100 for storing program instructions and data.
• Theinter-networking device354 includes a plurality ofports1106. Eachport1106 includes a suitable interface for coupling physical communication media to theinter-networking device1106. Each such interface includes, for example, a mechanical structure for attaching the physical communication media to theinter-networking device354 and a physical layer device (PHY) to send and receive signals over the attached communication media. In one such embodiment, theports1106 are ETHERNET ports.
• Thesoftware1102 comprisesinter-networking functionality1108 that causes theinter-networking device354 to perform one or more inter-networking functions for which it was designed. Examples of inter-networking functions include Layer 1, Layer 2, and Layer 3 (of the OSI model) inter-networking functions such as the routing, switching, repeating, bridging, and grooming of communication traffic that is received at theinter-networking device354 via the plurality ofports1106.
• Thesoftware1102 also comprisesmanagement functionality1110 that enables theinter-networking device354 to be configured and managed. In the particular embodiment shown inFIG. 11, themanagement functionality1110 includes a web server (and related web content and applications) that enables a user to directly interact with theinter-networking device354 using a web browser. In this embodiment, themanagement functionality1110 also includes SNMP functionality for interacting with an NMS (such as NMS380) using the SNMP protocol. SNMP commands and responses are communicated over the one ormore IP networks350 via one or more of theports1106 of theinter-networking device354.
• Thesoftware1102 also includes physical layer information (PLI)functionality1112. ThePLI functionality1112 is configured to retrieve physical layer information from theaggregation point353 and provide it to theinter-networking functionality1108. Theinter-networking functionality1108 uses the retrieved physical layer information to perform one or more inter-networking functions. In the embodiment shown inFIG. 11, thePLI functionality1112 retrieves physical layer information from theaggregation point353 using the API820 (shown inFIG. 8) implemented by theaggregation point353. To do this, thePLI functionality1112 supports the protocol used by theAPI820. Thesoftware1102 in theinter-networking device354 communicates with theaggregation point353 over the IP networks350. Theaggregation point software800 executing on theaggregation point353 processes and responds to API calls from theinter-networking device354. Theinter-networking device354 can also retrieve at least some of the physical layer information from an NMS or other network element.
• Some communication protocols (for example, the IEEE 802.3 family of ETHERNET standards) include functionality for automatically determining a suitable communication rate for a given communication link (for example, the IEEE 802.3 auto-negotiation, auto-sensing, and auto-fallback features). This type of functionality performs tests to make such determinations. In other words, the physical communication media is still, from the perspective of such an inter-networking device, a “black box.” The physical layer information provided to theinter-networking functionality1108 by thePLI functionality1112 enables theinter-networking functionality1108 to treat the physical layer as a “white box” for which it has accurate information to use in carrying out its inter-networking functions (for example, to use in making bridging, routing, or switching decisions). In one implementation of such an embodiment, the physical layer information received from theaggregation point353 is provided to theinter-networking functionality1108 to assist it in performing such auto-rate selection procedures.
• Moreover, where such conventional rate-determination functionality is used in making inter-networking decisions (such as, decisions as to which port to route data on), such conventional functionality is typically only able to characterize communication links that are directly connected to the inter-networking device. This means that if there is a segment of physical communication media that is one or more “hops” away from the inter-networking device that is of a lower quality (for example, because it supports lower communication rates) than the physical communication media used to implement the link that is directly attached to the inter-networking device, the inter-networking device would be unaware of that fact and would not take that fact into account in make routing or other inter-networking policy decisions. In the embodiment shown inFIG. 11, the physical layer information received from the aggregation point353 (and from other sources such as the NMS380) can be used to identify such situations and respond accordingly.
• The physical layer information received from theaggregation point353 can be used in other ways. For example, theinter-networking functionality1108 can be configured to constrain the routing of communication traffic by a policy that dictates that traffic received on someports1106 can only be communicated through certain areas of a building or buildings (for example, only through “secure” areas of the building). In order for such a policy to be enforced, theinter-networking functionality1108 needs to know where traffic that is output on each of itsports1106 will pass. The physical layer information received from theaggregation point353 can be used to make such determinations.
• In another example, theinter-networking functionality1108 is configured to enforce a policy that requires only certain types of physical communication media to be use with it (for example, requiring the use of certain brands or types or lengths of patch cords). The physical layer information received from theaggregation point353 can be used by theinter-networking functionality1108 to enforce such a policy (for example, by not forwarding data received onports1106 that have non-compliant media connected to them and/or by raising alarms or warnings when non-compliant media is connected to a port1106). In other words, theinter-networking functionality1108 can be configured to act as a “bus guardian” that enforces a “virtual keying” scheme in which at least some of the media information stored in or on apatch cord312 is used to “key” thepatch cord312.
• As noted above in connection withFIG. 1, inter-networking devices can also include media reading interfaces to read media information that is stored in or on the segments of physical media that are attached to its ports and to communicate the media information it reads from the attached segments of media (as well as information about the inter-networking device itself) to an aggregation point. For example, as shown inFIG. 11, eachport1106 has an associatedmedia reading interface1120 that theprogrammable processor1100 uses to read media information that is stored in or on the segments of physical media that are attached to itsports1106. Theprogrammable processor1100 in this example communicates the media information that it has read to a suitable aggregation point using one or more of the communication links that are established via one of itsports1106.
• In other implementations, theinter-networking device354 does not include media reading interfaces, and the physical layer information related to the physical media attached to its ports is provided to an aggregation point in other ways (for example, by manually entering and uploading the information).
• FIG. 12 illustrates another example of how physical layer information that is captured and aggregated using the techniques described here can be used to improve the efficiency of the inter-networking devices used in a network. In the example shown inFIG. 12, thenetwork1200 is implemented as a mesh network of Layer 2 devices1202 (typically ETHERNET switches) that bridge variousETHERNET LAN segments1204 together. In such anETHERNET network1200, a minimum spanning tree is constructed and those links that are not part of the spanning tree are disabled by disabling the corresponding ports of theswitches1202. As a result, a single active path exists between any two nodes in thenetwork1200. One or more redundant links can also be defined to provide backup paths that can be used if a link in the active path fails. The spanning tree is constructed in order to avoid loops.
• In conventional ETHERNET networks, a spanning tree protocol that complies with the IEEE 802.1D MAC Bridges standard is used to construct a spanning tree for the network. However, the spanning tree algorithm used in conventional ETHERNET networks is a “distributed” algorithm, in which the relevant switch must learn what devices are connected to it, exchange messages with the other switches, take part in electing a root bridge, and maintain a forwarding database. Also, when a new switch is added to the network, all the switches in the network must be informed by the root bridge of any topology changes that result from adding the new switch, in which case the other bridge devices must update the forwarding databases they maintain.
• Because a distributed spanning tree protocol is used in conventional ETHERNET networks, each switch must include sufficient processing power to implement the spanning tree protocol and to perform database look-ups when making decisions regarding how to forward packets it receives. In addition, changes to the spanning tree topology can take a significant amount of time to propagate through the network, which may lead to degraded network performance or, in some cases, loops. Also, the degree to which a conventional switch can learn about the network is limited, which can also lead to degraded network performance.
• Moreover, each such conventional switch typically uses transparent bridging to forward packets using the forwarding database. The forwarding database is initially empty and entries are added to the database as the switch receives packets. When a switch receives a packet, it inspects the source MAC address of the packet and adds an entry to the forwarding database for that source MAC address (if one does not already exist) that associates that MAC address with the port on which the packet was received. The switch also inspects the destination MAC address of the packet and searches for an entry in the forwarding database for that destination MAC address. If an entry is not found in the forwarding database for that destination MAC address, the packet is flooded to all other ports of the switch. In the future, when the switch receives a packet from the device that has that MAC address as its source MAC address, the switch adds an entry to its forwarding database that associates that MAC address with the port on which the packet was received. In this way, the switch is able to build up a forwarding database over time. The forwarding database needs to be updated as the topology of the network changes (for example, due to a patch cord being moved or removed, failure of links, the addition or deletion of a switch, or the movement of an end-user device).
• Because the forwarding database is maintained separately in each switch in a conventional ETHERNET network, each such switch must have sufficient processing power to perform such processing. Also, when the network topology changes occur, the performance of the network can be degraded, as the switches flood the network in order to learn the new topology of the network.
• In the example shown inFIG. 12,centralized bridge functionality1206 is deployed in thenetwork1200 to alleviate some of the problems noted above. Thecentralized bridge functionality1206 interacts with the one ormore aggregation points1208 that aggregate physical layer information for thenetwork1200. In the particular example shown inFIG. 12, thecentral bridge functionality1206 is deployed in anNMS1210. Theaggregation point1208 collects the MAC addresses of theend devices1212 that are on thenetwork1200 as well as information about theswitches1202.
• In the example shown inFIG. 12, for some of theend devices1212, media information for each segment of physical media that connects eachsuch end device1212 to aswitch1202 is automatically read and communicated to anaggregation point1208. That is, theend devices1212 include an appropriate media reading interfaces and driver software to read media information that is stored on an ETHERNET cable connected to thatend device1212 and provide the media information for the ETHERNET cable, as well the MAC address for theend device1212 and its current IP address, to anaggregation point1208. If theend device1212 is connected to aswitch1202 via one or more intermediary devices (such as a wall outlet and one or more patch panels), each such intermediary device would include appropriate media reading interface functionality to read the media information and provide to theaggregation point1208. In this way, theaggregation point1208 would be able to associate the MAC address of eachsuch end device1212 with a port of theswitch1202.
• Also, in the example shown inFIG. 12, for some of theend devices1212, media information for at least one segment of physical communication media that connects eachsuch end device1212 to aswitch1202 is not automatically read and communicated to anaggregation point1208. For theseend devices1212, physical layer information for each segment of physical communication media that connects theend devices1212 to ports of theswitch1202 and the MAC addresses for theend devices1212 can be manually entered and uploaded to the aggregation point1208 (as described above). Alternatively, thecentral bridge functionality1206 and/or the aggregations point1208 can obtain such information in other ways. For example, the associations between the MAC addresses of theend devices1212 and the ports of theswitch1202 can be learned from theNMS1210.
• Thecentral bridge functionality1206 uses the physical layer information and MAC address information it has received to associate the MAC address for eachend device1212 with the port of theparticular switch1202 to which theend device1212 is connected. Then, thecentral bridge functionality1206 determines a minimum spanning tree for thenetwork1200 using that information and determines a corresponding STP state (typically, “blocking”, “forwarding”, or “disabled”) for each port of eachswitch1202. Thecentral bridge functionality1206 then determines how the forwarding database for each of theswitches1202 should be configured based on the spanning tree and the MAC address information thecentral bridge functionality1206 has. The port state information and forwarding database information is then communicated to each of theswitches1202.
• Each of theswitches1202 includes correspondingbridge functionality1214 to receive the port state information and forwarding database information from thecentral bridge functionality1206. Thebridge functionality1214 in eachswitch1202 configures theswitch1202 so that each port is in the particular STP state specified by thecentral bridge functionality1206 for it. Also, thebridge functionality1214 in eachswitch1202 uses the forwarding database information it receives from thecentral bridge functionality1206 to configure itsforwarding database1216.
• When changes occur to thenetwork1200, the aggregation point1208 (and/or the other source of MAC address information such as the NMS1210) will see the changes and provide updated information to thecentral bridge functionality1206. Thecentral bridge functionality1206 can modify the spanning tree topology, if needed, and determine what (if any) changes to each switch's port states and forwardingdatabases1216 need to be made in response to the changes in thenetwork1200.
• By having thecentral bridge functionality1206 determine the spanning tree for thenetwork1200 and configure theforwarding databases1216 in theswitches1202, theswitches1202 need not perform such processing and, instead, the resources in theswitch1202 can be dedicated to forwarding packets. Also, thecentral bridge functionality1206 is able to directly learn of changes in thenetwork1200 from theaggregation point1208 and quickly respond to such changes and communicate any needed changes to theswitches1202. All of this should improve the performance of thenetwork1200. Moreover, thecentral bridge functionality1206, because it has access to more information about thenetwork1200, can more effectively create the spanning tree (for example, by assembling the spanning tree based on the type, number, location, length, etc. of physical communication media used to implement the various logical communication links in the network1200).
• FIG. 13 illustrates an alternative embodiment of asystem300′ that includes physical layer information functionality as well as physical layer management functionality. Thesystem300′ is similar to thesystem300 ofFIG. 3 except as described below. Those elements of thesystem300′ that are same as the corresponding elements ofsystem300 are referenced inFIG. 13 using the same reference numerals, and the description of such elements is not repeated below in connectionFIG. 13.
• The main difference between thesystem300 ofFIG. 3 and thesystem300′ ofFIG. 13 is that, in thesystem300′ ofFIG. 13, the master processor unit and slave processor unit are combined together into a single combined master/slave processor unit330/318 that is included in eachpatch panel302′. That is, eachpatch panel302′ includes themaster processor unit330 unit functionality shown inFIG. 6 (for example, eachpatent panel302′ includesmaster processor332 and ETHERNET interface340). Also, eachpatch panel302′ directly communicates with anappropriate aggregation point353. As a result, a backplane is not needed to communicate between the master processor unit functionality and the slave processor unit functionality.
• FIGS. 14-16 illustrate yet another alternative embodiment of asystem300″ that includes physical layer information functionality as well as physical layer management functionality. Thesystem300″ is similar to thesystem300 ofFIG. 3 except as described below. Those elements of thesystem300″ that are same as the corresponding elements ofsystem300 are referenced inFIGS. 14-16 using the same reference numerals, and the description of such elements is not repeated below in connectionFIGS. 14-16.
• The main difference between thesystem300 ofFIG. 3 and thesystem300″ ofFIGS. 14-16 is that thepatch panels302″ and theMPU330″ communicate over amain bus328 using protocols specified in the Institute of Electrical and Electronics Engineers (IEEE) 802.14.5 standard. Although the IEEE 802.14.5 protocols are typically used for wireless communications, in the embodiment shown inFIGS. 14-16, thepatch panels302″ andMPU330″ use the IEEE 802.14.5 protocols to communicate over one or more CATV coaxial cables.
• In such an embodiment, themain bus328 is physically implemented using one or more coaxial cables, where the data communications are communicated along the coaxial cables in a suitable radio frequency band and where theMPU330″ supplies DC power over the coaxial cables for use by the active components of eachpatch panel302″. Theslave processor module318″ in eachpatch panel302″ includes a suitable bus interface326 (shown inFIG. 15) to couple theslave processor320 to themaster processor module330″, and themaster processor unit330″ includes a suitable bus interface338 (shown inFIG. 16).
• In such an embodiment, thepatch panel software322 and themain bus interfaces326 of each patch panel″302 and theMPU software334 and the main bus interface338 of theMPU330″ comprises suitable functionality to enable theprogrammable processor320 in eachpatch panel302″ and theprogrammable processor332 in theMPU330″ to send and receive data using the IEEE 802.14.5 protocol as well as connectors (such as “F” connectors) to connect eachpatch panel302″ and theMPU330″ to the coaxial cables used to implement the main bus328 (via for example, a tap or splitter). The addressing scheme of the IEEE 802.14.5 protocols supports up to 127 patch panels (eachpatch panel302′ supporting up to 48 ports, for a total of 6096 ports) and oneMPU330″. The IEEE 802.14.5 protocols are designed for low-power applications, which is especially well-suited for use in the embodiment shown inFIGS. 14-16.
• Also, in the embodiment shown inFIG. 14-16, power is supplied to eachpatch panel302″ (more specifically, to the active components of eachpatch panel302″) over themain bus328. ThePSU344 in theMPU330″ converts the external power received from theexternal power source346 to power that is suitable for use by the components of theMPU330″ and for supply to thepatch panels302″.
• FIG. 17 is a block diagram of one embodiment of awall outlet1700 that includes functionality to obtain physical layer information. The embodiment of awall outlet1700 shown inFIG. 17 is described here as being implemented for use with thesystem100 ofFIG. 1, though other embodiments can be implemented in other ways.
• Thewall outlet1700 is configured to be installed in or on a wall or similar structure. Thewall outlet1700 includes a set ofports1702 similar to the ports described above in connection withFIGS. 1-16. Theports1702 are also referred to here as “downstream”ports1702. In general, eachdownstream port1702 includes a respective front connector (or other attachment point) in which a connectorized cable (or other segment of physical media) can be attached. An example of such a connectorized cable is a twisted-pair cable having RJ-45 plugs at each end. Eachdownstream port1702 also includes a rear attachment point that is connected to a corresponding port of aswitch1708. Theswitch1708 is used to communicatively couple each of thedownstream ports1702 to a patch panel (not shown inFIG. 17) over a single cable, which is attached to thewall outlet1700 via anupstream port1712. In one implementation of such an embodiment, theupstream port1712 is configured to be used with a non-connectorized cable. This cable is typically routed through a building (for example, over, under, around, and/or through walls, ceilings, floors, and the like) and is typically not easily or frequently moved.
• Theswitch1708 includes aswitching function1710 that switches data packets among thedownstream ports1702 and theupstream port1712. Theswitching function1710 is implemented, for example, in software, hardware, or combinations thereof.
• Thedownstream ports1702 of thewall outlet1700 are configured to be used with connectorized cables that have media information stored in or on them (for example, as described above in connection withFIGS. 1-16). Thewall outlet1700 includes amedia reading interface1704 for eachdownstream port1702. In this embodiment, the media readinterfaces1704 are implemented in the same manner as the media reading interfaces described above in connection withFIGS. 1-16. Eachmedia reading interface1704 is used to read the media information stored in or on the connectorized cable that is inserted into the correspondingdownstream port1702. The media information that is read from the connectorized cables that are inserted into thedownstream ports1702 is communicated from themedia reading interfaces1704 to aprogrammable processor1706. In the embodiment shown inFIG. 17, theprogrammable processor1706 is a part of theswitch1708.
• Theprogrammable processor1706 executes software that is similar to the software that is executed by the programmable processors described above in connection withFIGS. 1-16 (including, for example, a web server or other software that enables a user to interact with the processor1706). The main difference is that theprogrammable processor1706, in the embodiment shown inFIG. 17, communicates with a suitable aggregation point using the logical communication link that is provided using theupstream port1712. Thewall outlet1700 can be used to capture, and communicate to a suitable aggregation point, physical layer information related to thewall outlet1700 itself, the connectorized cables inserted into thedownstream ports1702, and the non-connectorized cable attached to theupstream port1712.
• As noted above, the techniques described here for reading media information stored in or on a segment of physical communication media can be used in one or more end nodes of the network. For example, computers (such as, laptops, servers, desktop computers, or special-purpose computing devices such as IP telephones, IP multi-media appliances, and storage devices) can be configured to read media information that is stored in or on the segments of physical communication media that are attached to its ports and to communicate the media information it reads from the attached segments of media (as well as information about the device itself) to an aggregation point.FIG. 18 is one embodiment of such acomputer1800. Thecomputer1800 includes a network interface card (NIC)1802 that is used to connect thecomputer1800 to an IP network (for example, an ETHERNET local area network). TheNIC1802 includes aport1804 that is used to physically attach a suitable cable (for example, a CAT-5/6/7 cable) to theNIC1802. TheNIC1804 also includesstandard NIC functionality1806 for communicating over the IP network (for example, a suitable physical layer device (PHY) and media access control (MAC) device). TheNIC1802 enables one or more processors1808 (and thesoftware1810 executing thereon) included in thecomputer1800 to communicate with the IP network. In this embodiment, theNIC1802 includes amedia reading interface1812 that the one ormore processors1808 use to read media information stored on or in the cable that is attached to thecomputer1800. The media information that is read from the cable, as well as information about theNIC1802 and the computer1800 (for example, any assigned MAC address or IP addresses) can be communicated to a suitable aggregation point as described above. In one implementation of such an embodiment, aNIC software driver1814 used with theNIC1802 includes physical layer information (PLI)functionality1816 that causes theprocessor1808 to read and communicate such physical layer information. TheNIC1802 andMRI1812 are coupled to theprocessor1808 using a suitable bus or other interconnect (not shown). In this way, information about thecomputer1800 can be automatically obtained and used in the various applications described.
• Functionality for reading media information stored in or on physical communication media can be integrated into one or more of the integrated circuits (or other circuits or devices) that communicate over the communication media. For example, functionality for reading such media information can be integrated into an ETHERNET physical layer device used in a switch. One such example is shown inFIG. 19.
• FIG. 19 is a block diagram of one exemplary embodiment of anETHERNET switch1900 that uses a physical layer device (PHY)1902 that includes integrated functionality for reading media information. In the particular exemplary embodiment shown inFIG. 19, thePHY1902 is in an octal ETHERNET PHY that includes ETHERNET physical layer functionality for eight ETHERNET ports (though it is to be understood that the techniques described here in connection withFIG. 19 can be used with physical layer devices having a different number of ports). In this embodiment, eight RJ-45jacks1904 are coupled to thePHY1902. Each of the RJ-45jacks1904 is configured to receive an RJ-45 plug attached to a CAT-5, 6, or 7 twisted-pair cable. For each RJ-45jack1904, the transmit conductors (TX+ and TX−) and receive conductors (RX+ and RX−) of that RJ-45jack1904 are coupled to transmit pins (TX+ and TX−) and receive pins (RX+ and RX−), respectively, of thePHY1902 using appropriate isolation transformers (not shown) that are either integrated into thejack1904 itself or that are external to it.
• ThePHY1902 includes the required ETHERNET physical sublayers—including a Physical Medium Dependent (PMD) sublayer1908 (which includes an appropriate transceiver for the physical communication media that are used with the switch1900), a Physical Medium Attachment (PMA) sublayer1910 (which performs PMA framing, octet synchronization/detection, and scrambling/descrambling), and a Physical Coding Sublayer (PCS)1912 (which performs auto-negotiation and encoding/decoding). ThePHY1902 also includes an appropriate Medium Independent Interface (MII)1914 (for example, a Medium Independent Interface, a Reduced Media Independent Interface (RMII), a Gigabit Media Independent Interface (GMII), and/or a Serial Media Independent Interface (SMII)) to connect thePHY1902 to an ETHERNET media access control (MAC)device1916. As noted above, in the particular exemplary embodiment shown inFIG. 19, thePHY1902 is designed for use in anETHERNET switch1900 and, as a result, theMAC1916 is a switch MAC device that includes appropriate functionality to implement an ETHERNET switch.
• ThePHY1902 typically also includes other standard ETHERNET physical layer functionality. For example, thePHY1902 includesmanagement functionality1920 for controlling and managing thePHY1902 and a management data input/output (MDIO) interface for communicating management information between thePHY1902 and theMAC1916. Other standard ETHERNT physical functionality includes, Medium Dependent Interface Cross-Over (MDIX) functionality and clock functionality (both of which are not shown inFIG. 19).
• In the exemplary embodiment shown inFIG. 19, each RJ-45jack1904 includes amedia reading interface1906 that can be used to determine if an RJ-45 plug is inserted into that RJ-45jack1904 and, if one is, to read the media information stored in an EEPROM attached to the RJ-45 plug (if there is one). Example configurations of such amedia interface1906 and a suitable RJ-45 plug are described above and in the '395 Application, the '208 Application, and the '964 Application.
• In this embodiment, a four linemedia reading interface1906 is used. One line is used for communicating data (using a serial data protocol), one line is used for power, and one line is used for ground. In this particular embodiment, a fourth line is also provided for potential future possible uses or upgrades.
• ThePHY1902 includes appropriate pins (or other inputs) for connecting to each of the eight media reading interfaces1906. ThePHY1902 also includes physical layer information (PLI)functionality1918 that is coupled to the eight media reading interfaces1906.
• In the particular exemplary embodiment shown inFIG. 19, thePLI functionality1918 is configured to provide the power and ground signals on the power and ground lines of each of the media reading interfaces1906. For example, thePLI functionality1918, in one implementation, is connected to the main power input of thePHY1902 in order to provide a suitable power signal on the power lines of each of the media reading interfaces1906. Also, thePLI functionality1918 is connected to the main ground input of thePHY1902 in order to provide a connection to ground for each of the ground lines of the media reading interfaces1906.
• In the particular exemplary embodiment shown inFIG. 19, thePLI functionality1918 is configured to monitor the eightmedia reading interfaces1906 and determine when an RJ-45 plug has been inserted into each of the RJ-45jacks1904. This can be done using the schemes described in the '395 Application, the '208 Application, and the '964 Application. ThePHY device1902 includes one or more registers1922 (also referred to here as “PLI registers”1922) in which thePLI functionality1918 stores PLI-related information. One byte of the PLI register1922 (also referred to here as the “state byte”) is used to store information about the state of each of the eightjacks1904, where each bit of the state byte represents the state of a respective one of thejacks1904. When the state of aparticular jack1904 changes (that is, when a plug is inserted into a previouslyempty jack1904 or a plug is removed from a jack1904), thePLI functionality1918 is able to detect such change and change the state of the corresponding bit in the state byte stored the PLI registers1922.
• ThePLI functionality1918 in thePHY device1902 is also configured to, when instructed to do so, read the media information stored in an EEPROM (if there is one) attached to an RJ-45 plug that is inserted into ajack1904. Data that is read from the EEPROM is stored in the PLI registers1922 of thePHY device1902. Also, thePLI functionality1918 is configured to, when instructed to do so, write data stored in the PLI registers1922 to an EEPROM attached to an RJ-45 plug that is inserted into ajack1904.
• In the particular exemplary embodiment shown inFIG. 19, ahost processor1930 is coupled to theMAC device1916 via an appropriate host interface. Thehost processor1930 executes software1932 (also referred to here as the “host software”). Thehost software1932 comprises program instructions that are stored (or otherwise embodied) on an appropriate storage medium or media from which at least a portion of the program instructions are read by thehost processor1930 for execution thereby.
• In this exemplary embodiment, thehost processor1930 includes a TCP/IP stack1934 andmanagement software1936 that implements various management and configuration related functionality (for example, a Simple Network Management Protocol (SNMP) agent and a web and/or TELNET server by which a user can interact with themanagement software1936 running on the switch1900).
• In the exemplary embodiment shown inFIG. 19, thehost software1932 also includesPLI software1938 that is configured to communicate physical layer information associated with theswitch1900 and the cables connected to it to an aggregation point over the network to which theswitch1900 is connected. In one implementation of theswitch1900, thePLI software1938 implements the protocols described above to participate in the discovery processing supported by the aggregation point and to send PLI to the aggregation point. Also, in other implementations, thePLI software1938 interacts with an aggregation point solely using the API (or other external interface technology) that the aggregation point provides for application-layer functionality to interact with it. In yet other implementations, thePLI software1938 interacts with the aggregation point via a NMS or other intermediary device or system (for example, using a protocol supported by the NMS such as SNMP).
• ThePLI software1938 executing on thehost processor1930 periodically reads the state byte stored in the PLI registers1922 in thePHY1902 by instructing the MAC device1916 (via the host interface between thehost processor1930 and the MAC device1916) to read the contents of the state byte (via the MDIO interface between theMAC device1916 and the PHY device1902).
• When an RJ-45 plug is inserted into ajack1904, thePLI software1938 executing on thehost processor1930 will learn of that fact when it reads the state byte stored in the PLI registers1922 of thePHY device1902. Then, thePLI software1938 causes (via the host interface between thehost processor1930 and the MAC device1916) theMAC device1916 to instruct (via the MDIO interface between theMAC device1916 and the PHY device1902) thePLI functionality1918 in thePHY device1902 to read the media information stored in the EEPROM (if any) attached to the newly inserted RJ-45 plug. ThePLI functionality1918 in thePHY device1902 stores the media information it reads from the EEPROM in the PLI registers1922. Once this is complete, thePLI software1938 can obtain that media information by causing (via the host interface between thehost processor1930 and the MAC device1916) theMAC device1916 to read (via the MDIO interface between theMAC device1916 and the PHY device1902) the correspondingPLI registers1922 in thePHY device1902. The media information read by theMAC device1916 is then provided to thePLI software1938 via the host interface. ThePLI software1938 can then communicate that information to an aggregation point as described above.
• In addition to communicating PLI about theswitch1900 and any cables connected to thejacks1904 of theswitch1900, theswitch1900 can also implement one or more of the inter-networking features described above in connection withFIGS. 11-12.
• Another example of an ETHERNET physical layer device having integrated functionality for reading media information stored in or on physical communication media is shown inFIG. 20.FIG. 20 is a block diagram of one exemplary embodiment of acomputer2000 that uses a physical layer device (PHY)2002 that includes integrated functionality for reading media information. The functionality for reading media information stored in or onCAT 5, 6, or 7 cables is integrated into thePHY2002 in the same manner as described above in connection withFIG. 19. Accordingly, elements of thecomputer2000 that are substantially similar to corresponding elements described above in connection withFIG. 19 are referenced inFIG. 20 using the same text labels as used inFIG. 19 and reference numerals with the same last two digits as those used inFIG. 19.
• One difference between thePHY2002 ofFIG. 20 and thePHY1902 ofFIG. 19 is in the number ETHERNET ports supported. ThePHY2002 ofFIG. 20 supports a single ETHERNET port. Also, theMAC device2016 ofFIG. 20 is a MAC device suitable for use in an end node device such as acomputer2000. Likewise, thesoftware2032 executing on thehost processor2030 is software that is typically executed by an end-user computer2000.
• AlthoughFIGS. 19 and 20 illustrate particular examples of how functionality for reading media information stored on or in physical communication medium can be integrated into one or more of the integrated circuits (or other circuits or devices) that communicate over the communication media, it is to be understood that such media reading functionality can be integrated in other ways.
• In other embodiments, media information is stored in or on unconnectorized cables or other physical communication media. For example, in one such embodiment, storage devices are attached near each end of the unconnecterized cable so that when each end of the cable is attached to a respective attachment point, an interface for a respective one of the storage devices mates with a corresponding media reading interface located on or near the attachment point so the information stored in the storage device can be read from the storage device in a similar manner as is described above. Such embodiments can include punch down connections for connecting copper twisted pair cables to the rear sides of RJ jacks or to Krone-type blocks that include Insulation Displacement Connectors (IDC's).
• FIG. 21 is a diagram of one embodiment of ajacket2100 that can be fitted around an RJ-45 plug in order to attach a storage device to the RJ-45 plug. Thejacket2100 is formed as a molded,flexible circuit2102 that has twoside walls2104 and atop wall2106. Theflexible circuit2102 is formed from one or more flexible films (for example, one or more polymer films) and is configured to fit snuggly around an RJ-45 plug so that thejacket2100, once placed around the plug, will remain securely affixed to the RJ-45 plug.
• In the embodiment shown inFIG. 21, a storage device2108 (for example, an EEPROM or other non-volatile memory device) is mounted on the outer surface of thetop wall2106 of the molded,flexible circuit2102. The storage device interface for mating with a media reading interface comprises a set ofconductive leads2110 that are formed on the outer surface of thetop wall2106 and extend down the outer surface of bothside walls2104. At least a portion of theleads2110 are exposed (that is, do not have an insulator formed over them) so that corresponding contacts from a media reading interface can come into contact with theleads2110 when the plug around which thejacket2100 is attached is inserted into a port. In such an embodiment, the contacts of the media reading interface can be spring-loaded into order to press against theleads2110 in order to form a good electrical contact. The media reading interface can then be used to read the information stored in the storage device1508 in the manner described above.
• Also, in this embodiment, an infra-red emitter2112 is mounted on the outer surface of thetop wall2106. The infra-red emitter2112 is configured to emit an infra-red signal on which at least a portion of the information stored in thestorage device2108 is encoded. In one implementation, the infra-red emitter2112 is configured to output this infra-red signal with the information encoded thereon whenever thestorage device2108 is read using the media reading interface. Thejacket2100 is configured so that a technician can position an infra-red detector near the infra-read emitter2112 in order to receive the infra-red signal that is emitted. The infra-red detector can be coupled to, for example, a hand held unit that decodes the received infra-red signal and displays the information that was encoded on the infra-red signal. In this way, a technician can view the information that is stored in thestorage device2108 without requiring the RJ-45 plug to be removed from a port. This embodiment can be adapted for other connector types, including fiber optic connectors
• The PLI information that is captured, maintained, and made available using the techniques described here can be used for many different types of applications. For example, the PLI information can be used in managing the amount of slack that is associated with each media segment in the system. When a new patch cord (or other media segment) is needed to be installed in the network, the physical layer information that has been captured can be used to determine a precise and appropriate length for the patch cord based on the PLI and the particular slack-management policies that are used by the enterprise or carrier. Also, such PLI can be used to assist with public safety applications (for example, to help to locate devices that are used in a voice-over-Internet Protocol (VOIP) telephony system).
• Examples of how such physical layer information can be used include the following. For example, a NMS (or other user interface associated with theaggregation point120 or anyconnector assembly102 such aspatch panel302 or302′), when displaying information about a particular segment of physical media, can also be configured to automatically send the user to a web site via which the user can order a replacement for that particular media segment. For example, a Web-browser based user interface can be configured to display a button (or other user interface element) that a user can click on in order to automatically bring up a web site via which a replacement segment can be ordered. Similar functionality can be included in the user interfaces that are displayed by the aggregation points120 and connector assemblies104 (for example, by the web servers that execute on the aggregation points102 and the connector assemblies104 (for example,patch panels302 or302′)).
• In another example, when a particular lot of physical communication media segments is recalled (for example, due to safety or performance concerns), the physical layer information that is obtained in the manner described here can be used to determine if and where any of the recalled segments of physical media are deployed in the network. This information can be used in determining whether to replace the segment and/or can be used in actually replacing the segment.
• In another example, the physical layer information described here is used for intrusion detection. For example, for particular secure resources on a network (for example, a particular server or service), a security policy can be established that specifies that the secure resources should only be accessed by specific computers that are coupled to the secure resource using particular ports of particular inter-networking devices or other connector assemblies and particular segments of physical communication media. If someone attempts to access the secure resources in a manner that does not comply with the security policy, he or she is not granted access to the secure resources. For example, if an intruder were able to spoof the identify of an authorized computer but accessed the secure resource using an unauthorized logical communication link, the intruder would still be denied access to the secure resource unless the intruder is able to spoof the identities of all of the other elements identified in the policy (for example, the identities of all the physical communication media that implement the logical communication link between the computer and the secure resource).
• In another example, the aggregation point receives and store information about certain conditions that exist in various locations in which the physical communication media is deployed. For example, the aggregation point can be configured to receive and store information that is unique to each location (such as, local requirements concerning the use of battery backups, environmental conditions obtained from external sensors and external systems (such as external temperature sensors, HVAC systems, or computer servers that provide weather related information)). Routing decisions within the network can then be made, at least in part, based on such locally unique conditions.
• In another example, a technician near aparticular patch panel302 may want to swap out a particular patch cord (for example, because a visual inspection of the patch cord identified some potential issue with the patch cord). A request for clearance to disconnect the patch cord from the associatedport304 would be routed to an aggregation point or a NMS. The aggregation point or NMS would send messages to one or more relevantinter-networking devices354 indicating that a patch cord used to implement a particular logical communication link is going to be disconnected in the near future. Theinter-networking devices354, in response to such a signal, would route certain classes of traffic (for example, real-time traffic such as telephony or multimedia traffic) away from that logical communication link. Also, theinter-networking devices354 can be configured to communicate an “all clear” signal back to the aggregation point or NMS, which indicates that it is okay, from the perspective of each such device, to disconnect the relevant patch cord. When the aggregation point or NMS receives all-clear signals from all the notified inter-networking devices, the aggregation point or NMS informs the technician (using the display315) that it is okay to disconnect that patch cord.
• In another example, the physical layer information obtained using the techniques described here is used to check if a particular type of physical communication media has been installed. For example, where an enterprise or carrier wishes to deploy a particular type of physical communication media for a given logical communication link (for example, CAT-6 compatible physical communication media to implement GIGABIT ETHERNET communication links), the physical layer information that is obtained as described above can be used to confirm that each physical communication media segment of the logical communication link has been implemented using the appropriate type of physical communication media. Another example is to confirm that multi-mode fiber or shielded twisted-pair cabling has been deployed instead of single-mode fiber or unshielded twisted-pair cabling, respectively, which may not be readily apparent from a visual inspection of the communication media when installed.
• In another example, the physical layer information obtained using the techniques described here is used for theft monitoring. For example, in the case of IP telephony, the IP telephony server can be configured to deliver telephony service to each IP phone only if that IP phone is used with particular logical communication links implemented using particular physical layer elements (for example, segments deployed within a given building). If the IP phone is stolen or moved outside of any authorized area, the IP telephony server does not provide service to the IP phone, even if it is able to access the IP telephony server.
• The techniques described here can be used in a variety of applications, including enterprise applications and carrier applications.
• FIGS. 22 and 23 illustrate one example of a carrier application.
• FIG. 22 illustrates anetwork2200 deploying passive fiber optic lines. As shown, thenetwork2200 can include acentral office2201 that connects a number of end subscribers2205 (also calledend users2205 herein) in a network. Thecentral office2201 can additionally connect to a larger network such as the Internet (not shown) and a public switched telephone network (PSTN). Thenetwork2200 can also include fiber distribution hubs (FDHs)2203 having one or more optical splitters (for example, 1-to-8 splitters, 1-to-16 splitters, or 1-to-32 splitters) that generate a number of individual fibers that may lead to the premises of anend user2205. The various lines of thenetwork2200 can be aerial or housed within underground conduits.
• The portion of thenetwork2200 that is closest tocentral office2201 is generally referred to as the F1 region, where F1 is the “feeder fiber” from thecentral office2201. The portion of thenetwork2200 closest to theend users2205 can be referred to as an F2 portion ofnetwork2200. Thenetwork2200 includes a plurality of break-outlocations2202 at which branch cables are separated out from the main cable lines. Branch cables are often connected to dropterminals2204 that include connector interfaces for facilitating coupling of the fibers of the branch cables to a plurality ofdifferent subscriber locations2205.
• Splitters used in anFDH2203 can accept a feeder cable F1 having a number of fibers and may split those incoming fibers into, for example, 216 to 432 individual distribution fibers that may be associated with a like number of end user locations. In typical applications, an optical splitter is provided prepackaged in an optical splitter module housing and provided with a splitter output in pigtails that extend from the module. The splitter output pigtails are typically connectorized with, for example, SC, LC, or LX.5 connectors. The optical splitter module provides protective packaging for the optical splitter components in the housing and thus provides for easy handling for otherwise fragile splitter components. This modular approach allows optical splitter modules to be added incrementally toFDHs2203 as required.
• FIG. 23 is a schematic diagram showing an example cable routing scheme for theFDH2203.
• TheFDH2203 generally administers connections at a termination panel between incoming fiber and outgoing fiber in an Outside Plant (OSP) environment. As the term is used herein, “a connection” between fibers includes both direct and indirect connections. Examples of incoming fibers include the feeder cable fibers that enter the cabinet and intermediate fibers (for example, connectorized pigtails extending from splitters and patching fibers/jumpers) that connect the feeder cable fiber to the termination panel. Examples of outgoing fibers include the subscriber cable fibers that exit the cabinet and any intermediate fibers that connect the subscriber cable fibers to the termination panel. TheFDH2203 provides an interconnect interface for optical transmission signals at a location in the network where operational access and reconfiguration are desired. For example, as noted above, theFDH2203 can be used to split the feeder cables and terminate the split feeder cables to distribution cables routed to subscriber locations. In addition, theFDH2203 is designed to accommodate a range of alternative sizes and fiber counts and support factory installation of pigtails, fanouts and splitters.
• As shown atFIG. 23, afeeder cable2320 is initially routed into theFDH2203 through acabinet2302. In certain embodiments, the fibers of thefeeder cable2320 can include ribbon fibers. Anexample feeder cable2320 may include twelve to forty-eight individual fibers connected to a service providercentral office2201. In some embodiments, after entering thecabinet2302, the fibers of thefeeder cable2320 are routed to a feeder cable interface2338 (for example, fiber optic adapter modules, a splice tray, etc.). At thefeeder cable interface2338, one or more of the fibers of thefeeder cable2320 are individually connected to separatesplitter input fibers2324. Thesplitter input fibers2324 are routed from thefeeder cable interface2338 to thesplitter module housing2308. At thesplitter module housing2308, thesplitter input fibers2324 are connected to separatesplitter modules2316, wherein theinput fibers2324 are each split intomultiple pigtails2326, each having connectorized ends2328. In other embodiments, however, the fibers of thefeeder cable2320 can be connectorized and can be routed directly to thesplitter modules2316 thereby bypassing or eliminating the need for an intermediatefeeder cable interface2338.
• When thepigtails2326 are not in service, the connectorized ends2328 can be temporarily stored on astorage module2318 that is mounted at thestorage region2306 of thecabinet2302. When thepigtails2326 are needed for service, thepigtails2326 are routed from thesplitter modules2316 to atermination module2310 that is provided at thetermination region2304 of thecabinet2302. At thetermination module2310, thepigtails2326 are connected to the fibers of adistribution cable2330. The termination panel is the dividing line between the incoming fibers and the outgoing fibers. Atypical distribution cable2330 forms the F2 portion of a network (seeFIG. 22) and typically includes a plurality of fibers (for example, 144, 216 or 432 fibers) that are routed from theFDH2203 tosubscriber locations2205.Cables2330 with connectorized ends2332 connect to the connectorized ends2328 of thepigtails2326 atfiber optic adapters2312.
• In some embodiments, one or more of the fibers of thefeeder cable2320 are not connected to any of thesplitter modules2316. Rather, these fibers of thefeeder cable2320 are connected to pass-throughfibers2334 having connectorized ends2336. The pass-throughfibers2334 are connected to thetermination modules2310, without first connecting to thesplitter modules2316. By refraining from splitting afiber2334, a stronger signal can be sent to one of the subscribers. The connectorized ends2336 of the pass-throughfibers2334 can be stored at thestorage region2306 when not in use.Cables2330 with connectorized ends2332 connect to the connectorized ends2336 of the pass-throughfibers2334 at thefiber optic adapters2312. Thefeeder interface device2338 includesconnections2322 for connecting the various cables, such as with splices or connectorized ends and adapters like connectorized ends2328 and2336 andadapters2312 noted above.
• The various segments of physical communication media that are used in thenetwork2200 ofFIGS. 22-23 can have identifier and attribute information stored in or on them. For example, the various connectorized fibers described above in connection withFIGS. 22-23 can be outfitted with storage devices and the corresponding termination modules (and other attachment points) can include corresponding media reading interfaces to read at least a portion of the identifier and attribute information stored in each of the storage devices. The identifier and attribute information that is read from the storage devices can be communicated to an aggregation point for use as described herein (using a suitable communication link such as a wireless or wired communication link). Other physical layer information (for example, information about the termination modules, splitters, cabinets, and other devices in the network and information about the locations in which they are deployed) can also be provided to such an aggregation point for use thereby.
• In another example, the physical layer information obtained using the techniques described here is used by a telecommunications carrier to assist fulfilling service level agreements. For example, as noted above, the physical layer information can be used to determine if a given logical communication link has been implemented using appropriate physical communication media (for example, CAT-6 cabling in ETHERNET in the First Mile (EFM) applications or the appropriate type of fiber). This may be especially important at the demarcation point between the telecommunication carrier's equipment and the customer's equipment. Also, physical layer information can be used to determine if unauthorized changes have been made at the demarcation point.
• In another example, the physical layer information obtained using the techniques described here is used by a telecommunications carrier to implement differentiated service levels. For example, where certain customers require their communications traffic to travel through certain geographic regions (for example, to comply with export control laws), a carrier can use the physical layer information obtained using the techniques described here to route the customers' traffic in compliance with the customers' requirements. In another example, each routing point, site, building, etc. is assigned a security score, and certain communication traffic is routed only through routing points, sites, buildings, etc. that have a security score at or above a certain level.
• A number of embodiments of the invention defined by the following claims have been described. Nevertheless, it will be understood that various modifications to the described embodiments may be made without departing from the spirit and scope of the claimed invention. Accordingly, other embodiments are within the scope of the following claims.

Claims (26)

What is claimed is:

1. A system comprising:

at least one patching device comprising a plurality of ports and a plurality of port interfaces, wherein the patching device is configured to use the port interfaces to automatically determine first information about connections of cables to the ports of the patching device;

an aggregation device, separate from the least one patching device, that is communicatively coupled to the patching device over a network;

wherein the aggregation device is configured to receive, from the at least one patching device, at least some of the first information;

wherein the aggregation device is further configured to receive second information indicative of the respective location of each of the ports of the patching device; and

wherein the aggregation device is further configured to store at least some of the first and second information received thereby in a data store associated with the aggregation device.

2. The system ofclaim 1, wherein the second information indicative of the respective location of each of the ports of the patching device comprises respective X, Y, and Z location information indicative of the respective location of each of the ports of the patching device.

3. The system ofclaim 1, wherein the second information indicative of the respective location of each of the ports of the patching device comprises respective ANSI/TIA/EIA 606-A Standard—Administration Standard For The Commercial Telecommunications Infrastructure X, Y, and Z location information indicative of the respective location of each of the ports of the patching device.

4. The system ofclaim 1, wherein the patching device is configured to use the port interfaces to automatically determine the first information about the connections of the cables to the ports of the patching device by detecting changes in a connection state of at least one of the ports.

5. The system ofclaim 1, wherein the patching device is configured to use the port interfaces to automatically determine the first information about the connections of the cables to the ports of the patching device by reading storage device information stored in a storage device that is a part of a connector that is a part of a cable connected to at least one port of the at least one patching device.

6. The system ofclaim 5, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read wirelessly.

7. The system ofclaim 6, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read wirelessly using an optical or infrared interface.

8. The system ofclaim 5, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read via one or more contacts connected to the storage device

9. The system ofclaim 5, wherein the storage device comprises non-volatile memory.

10. The system ofclaim 5, wherein the patching device is configured to write information to the storage device.

11. The system ofclaim 1, wherein at least one cable comprises at least one of a copper cable and an optical cable.

12. The system ofclaim 1, wherein at least one of the cables comprises an MPO connector.

13. The system ofclaim 1, wherein the plurality of ports comprises at least one MPO port.

14. A method for using in a system comprising at least one patching device comprising a plurality of ports, the method comprising:

automatically determining, by the at least one patching device using a plurality of port interfaces included in the at least one patching device, first information about connections of cables to the ports of the patching device;

receiving, by the aggregation device from the at least one patching device, at least some of the first information;

receiving, by the aggregation device, second information indicative of the respective location of each of the ports of the patching device; and

storing, by the aggregation device in a data store associated with the aggregation device, at least some of the first and second information received by the aggregation device.

15. The method ofclaim 14, wherein the second information indicative of the respective locations of each of the ports of the patching device comprises respective X, Y, and Z location information indicative of the respective location of each of the ports of the patching device.

16. The method ofclaim 14, wherein the second information indicative of the respective locations of each of the ports of the patching device comprises respective ANSI/TIA/EIA 606-A Standard—Administration Standard For The Commercial Telecommunications Infrastructure X, Y, and Z location information indicative of the respective location of each of the ports of the patching device.

17. The method ofclaim 14, wherein automatically determining the first information about the connections of the cables to the ports of the patching device comprises:

detecting changes in a connection state of at least one of the ports.

18. The method ofclaim 14, wherein automatically determining the first information about the connections of the cables to the ports of the patching device comprises:

reading storage device information stored in a storage device that is a part of a connector that is a part of cable connected to at least one port of the at least one patching device.

19. The method ofclaim 18, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read wirelessly.

20. The method ofclaim 19, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read wirelessly using an optical or infrared interface.

21. The method ofclaim 18, wherein the storage device of the connector of the cable connected to the at least one port of the at least one patching device is configured to be read via one or more contacts connected to the storage device

22. The method ofclaim 18, wherein the storage device comprises non-volatile memory.

23. The method ofclaim 18, further comprising:

writing, by the at least one patching device using at least one of the port interfaces, information to the storage device.

24. The method ofclaim 14, wherein at least one cable comprises at least one of a copper cable and an optical cable.

25. The method ofclaim 14, wherein at least one of the cables comprises an MPO connector.

26. The method ofclaim 14, wherein the plurality of ports comprises at least one MPO port.

Images