PHYSICAL LAYER MANAGEMENT AT A WALL PLATE DEVICE

This application is a continuation of U.S. patent application Ser. No. 13/937,314 filed Jul. 9, 2013 and entitled “PHYSICAL LAYER MANAGEMENT AT A WALL PLATE DEVICE”, which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/670,300, filed on Jul. 11, 2012 and entitled “PHYSICAL LAYER MANAGEMENT AT A WALL PLATE DEVICE”, each of which are hereby incorporated herein by reference.

Conventional physical layer management (PLM) systems are typically designed to track connections that are made at a patch panel. That is, historically conventional PLM systems have been “patch panel centric” and have not included functionality to track connections that are made at other types of devices and systems in a network. For example, such PLM systems typically do not automatically track connections that are made at a switch, router, hub, gateway, access point, server computer, end-user computer, appliance computers (such as network-attached storage (NAS) devices), and nodes of a storage area network (SAN) or other types of devices. Although there are management systems that are used to manage and collect information about such devices, such management systems are typically separate from the PLM systems used to track connections made at a patch panel.

One embodiment is directed to a wall plate device including one or more jacks. Each jack includes a rear attachment point configured to couple to one or more communication paths for non-service network traffic in a semi-permanent manner. Each jack also includes a front attachment point configured to mate with a connector of a corresponding physical communication media, and to couple such physical communication media to the one or more communication paths at the rear attachment point. Each jack also includes a media reading interface configured to interface with a PLM interface of a connector connected to the front attachment point. The wall plate device also includes a programmable processor coupled to each of the media reading interfaces and configured to access a storage device or other component of a connector connected to the front attachment point through the media reading interface to obtain physical layer management (PLM) information. The programmable processor is configured to communicate the PLM information to another device external to the wall plate device.

In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific illustrative embodiments. However, it is to be understood that other embodiments may be utilized and that logical, mechanical, and electrical changes may be made. Furthermore, the method presented in the drawing figures and the specification is not to be construed as limiting the order in which the individual steps may be performed. The following detailed description is, therefore, not to be taken in a limiting sense.

FIG. 1 is a block diagram of one example of a system including physical layer management at wall plate devices. The system is part of an IP network 126 which includes a plurality of network entities in a local area network (LAN) 104. The example network entities shown in FIG. 1 include a switch 160 (or other internetworking device such as a hub, bridge, router, or gateway), a patch panel 110, a first and second wall plate device 130, 150, as well as a first and second end user device 106a, 106c. The first and second nodes 106a, 106c are referred to herein as “end user devices” since they are outside of the core infrastructure (switch 160, patch panel 110, wall plate devices (130, 150) of the LAN 104 and can be coupled to the core infrastructure by an end user (e.g., through a wall plate device 130, 150).

Although a particular, number, type, and arrangement of network entities is shown in FIG. 1 it should be understood than any number, combination of types, and arrangement of network entities can be used, including more wall plate devices, wall plate devices coupled to more than one other network entity, etc. Examples of network entities 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, wall plate devices (also referred to as “wall 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). Examples of end user devices include, without limitation, computers, peripherals (such as printers, copiers, storage devices, and scanners), IP telephones, end user routers, end user switches, access points (e.g., wireless), networked TVs, set top boxes, and other such end user devices.

The network entities are coupled together using physical communication media 107. Each communication media 107 is a cable comprising one or more communication paths. The one or more communication paths can be formed by one or more fiber optics or one or more copper wires. As an example, the physical communication media 107 can be implemented using a simplex cable, a hybrid cable, a multi-channel cable, etc. Some physical communication media 107, such as media 107d, 107e, and 107g, include a first connector terminating a first end of the one or more communication paths and a second connector terminating a second (opposite) end of the one or more communication paths. Other examples of communication media 107, such as media 107a, 107c, can include a connector terminating a first end and a wall plate device 130, 150 terminating a second (opposite) end. In examples where the one or more communication paths are fiber optics, the connectors can be corresponding passive optical connectors or an active optical module for converting between optical signals and electrical signals. In examples where the one or more communication paths are copper wires, connectors can be a corresponding electrical connector. Some or all of the physical communication media 107 is a connectorized media segment. As used herein, a “connectorized” media segment is a segment of physical communication media that includes a connector at at least one end of the segment. The connectors are used to facilitate the easy and repeated attachment and unattachment of the media segment 107 to a jack.

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.

Example physical communication media 107 include duplex fiber optic cable including one or more optical fibers. The one or more optical fibers can include single-mode or multi-mode fibers. The fiber optic cable can include a simplex cable, duplex cable, 12-fiber cable, 24-fiber cable and other fiber optic cables (such as hybrid fiber/copper cables). Other example physical communication media 107 include coaxial cable. Still other examples include multiple-fiber cable including a multi-fiber connector (for example, a suitable MPO or MTP connector) at each end of such cable.

The patch panel 110 is used to cross connect various network entities of the local area network 104, and comprises a set of port (not shown). Each port is associated with a respective jack on the front face of the patch panel 107 into which a RJ-45 connector of a communication media 107 can be inserted. Various ports of the patch panel 107 can be connected to ports of the switch 160 by connecting one or more communication mediums 107g between the front jacks of the patch panel 107 and jacks of the switch 160.

Each port is also associated with a respective rear termination point at which a horizontal run of a communication media 107 can be terminated. Each port is configured to communicatively couple the jack associated with that port (and any communication media 107 inserted therein) to the respective termination point (and any horizontal run of communication media 107 terminated thereat). In this way, a patch cord inserted into the front jack of the port can be connected to the corresponding horizontal run of twisted-pair cabling terminated at the corresponding rear termination point.

In the example shown in FIG. 1, each horizontal run terminates at its other end at a wall plate device 130, 150. Two types of wall plate devices are shown in FIG. 1.

One type of wall plate device shown in FIG. 1 is a distribution wall plate device 130. The distribution wall plate device 130 is coupled to the patch panel 107 with the communication media 107a (e.g., a CAT-5 or CAT-6 cable). The distribution wall plate device 130 includes a termination point 132 at which a horizontal run of the communication media 107a can be terminated. A first connector of the communication media 107a is connected to a first jack of the patch panel 107 and a second end of the communication media 107a is attached to the termination point of the distribution wall plate device 130.

The distribution wall plate device 130 also includes a plurality of jacks 134 (for example, RJ-45 jacks) and an ETHERNET hub or switch 136. The termination point 132 for the horizontal run and each of the jacks 134 are coupled to a respective port of the ETHERNET hub or switch 136. In this way, each of the jacks 134 is communicatively coupled to the horizontal run terminated at the termination point 132, and the connectivity provided over the horizontal run can be shared by devices connected to the jacks 134. The distribution wall plate device 130 also includes a suitable power supply or interface (not shown) for providing power to the ETHERNET hub or switch 136. Examples of ways of providing power to the ETHERNET hub or switch 136 include using Power-Over-ETHERNET technology to provide power over the horizontal run of the communication media 107a and/or over one or more communication mediums 107d connected to the jacks 134. Power can also be provided by connecting the distribution wall plate device 130 to a conventional AC mains power outlet using an external or internal power adapter.

An end user device 106a of the network 104 is coupled to other network entities in the local area network 104 by connecting one end of a physical communication media 107d (e.g., a CAT-5 or CAT-6 cable) to the end user device 106a and the other end of the communication media 107d to one of the jacks 134 of the distribution wall plate device 130. In this example, the end user device 106a comprises a wireless access point, however, any device capable of connecting to the jack 134 and communicating over the network 104 can be used. The wireless access point 106a can be wireless coupled to another device 102.

Another type of wall plate device shown in FIG. 1 is a conventional passive wall plate device 150. The passive wall plate device 150 includes a termination point 124 for a horizontal run of the communication media 107c and a corresponding jack 154. The passive wall plate device 150 is coupled to the patch panel 107 with the communication media 107c (e.g., a CAT-5 or CAT-6 cable). A first connector at a first end of the communication media 107c is connected to a first jack of the patch panel 107 and a second end of the communication media 107c is attached to a termination point 132 of the passive wall plate device 150. Each conductor in the horizontal run of twisted-pair cabling (107c) is electrically connected to a corresponding conductor in the jack 154. In this way, the jack 154 is communicatively coupled to the horizontal run terminated at the termination point 124, and the connectivity provided over the horizontal run can be shared by any devices connected to the jack 154.

In the example shown in FIG. 1, an end user device 106c is connected to the local area network 104 by connecting one end of a communication media 107e (e.g., a CAT-5 or CAT-6 cable) to the end user device 106c and the other end of the communication media 107e to the jack 154 of the passive wall plate device 150.

At least some of the network entities are designed for use with segments of physical communication media 107 that have identifier and attribute information (also referred to herein as “PLM information”) stored in or on them.

The identifier and attribute information is stored in or on the segment of physical communication media 107 in a manner that enables the stored information, when the segment is attached to a jack (134, 154), to be read by a programmable processor associated with the network entity. Examples of PLM information that can be stored in or on a segment of physical communication media 107 include, without limitation, an identifier that uniquely identifies that particular segment of physical communication media 107 (similar to an ETHERNET Media Access Control (MAC) address but associated with the physical communication media 107 and/or connector attached to the physical communication media 107), 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 107 or a connector attached to the physical communication media 107 (such as information about the color or shape of the physical communication media 107 or connector or an image of the physical communication media 107 or connector), and other information used by an Enterprise Resource Planning (ERP) system or inventory control system. PLM information can also include testing or media quality or performance information which, for example, can be the results of testing that is performed when a particular segment of media 107 is manufactured. In other embodiments, alternate or additional data is stored in or on the media segments 107.

Also, as noted below, in some embodiments, the PLM information stored in or on the segment of physical communication media 107 can be updated. For example, the PLM information stored in or on the segment of physical communication media 107 can be updated to include the results of testing that is performed when a segment of physical media 107 is installed or otherwise checked. In another example, such testing information is supplied to an aggregation point 124 and stored in a data store maintained by the aggregation point 124. In another example, the PLM information stored in or on the segment of physical communication media 107 includes a count of the number of times that a connector attached to a segment of physical communication media 107 has been inserted into jack (134, 154). In such an example, the count stored in or on the segment of physical communication media 107 is updated each time the connector 102 is inserted into jack (134, 154). 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 107).

In the particular embodiment shown in FIG. 1, each of the jacks (134, 154) of the network entities 101 comprises a respective media reading interface via which the respective programmable processor is able to determine if a physical communication media segment 107 is attached to that jack (134, 154) and, if one is, to read the identifier and attribute information (PLM information) stored in or on the attached segment (if such information is stored therein or thereon). The programmable processor associated with each network entity is communicatively coupled to each of the media reading interfaces using a suitable bus or other interconnect.

Each programmable processor is configured to execute software or firmware that causes the programmable processor to carry out various functions described below. Each programmable processor also includes suitable memory that is coupled to the programmable processor for storing program instructions and data. In general, the programmable processor determines if a physical communication media segment 107 is attached to a jack (134, 154) with which that processor is associated and, if one is, to read the identifier and attribute information (PLM information) stored in or on the attached physical communication media segment 107 (if the segment 107 includes such information stored therein or thereon) using the associated media reading interface.

Each programmable processor is also configured to communicate physical layer information to devices that are coupled to the IP network 126. The physical layer information (PLI) includes information about the network entities associated with that programmable processor (also referred to here as “device information”) as well as information about any segments of physical media 107 attached to the jacks (134, 154) of those network entities (also referred to here as “PLM information”) The device information includes, for example, an identifier for each network entity, a type identifier that identifies the network entity's type, and jack priority information that associates a priority level with each jack. The PLM information includes identity and attribute information that the programmable processor has read from attached physical media segments 107 that have identifier and attribute information stored in or on it. The PLI may also include information about physical communication media 107 that does not have identifier or attribute information stored in or on it. This latter type of PLI can be manually input at the time the associated physical media segments 107 are attached to the network entity (for example, using a management application executing on the programmable processor that enables a user to configure and monitor the network entity).

The system includes functionality that enables the physical layer information that the network entities capture to be used by application-layer functionality outside of 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 in FIG. 1, the system includes an aggregation point 124 that is communicatively coupled to the network entities via the IP network 126.

The aggregation point 124 includes functionality that obtains physical layer information from the network entities (and other devices) and stores the physical layer information in a data store.

The aggregation point 124 can be used to receive physical layer information from various types of network entities that have functionality for automatically reading information stored in or on the segment of physical communication media 107. Examples of such network entities are noted above. Also, the aggregation point 124 and aggregation functionality 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 107. 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.

The aggregation point 124 can also be used to obtain other types of physical layer information. For example, in this embodiment, the aggregation point 124 also obtains information about physical communication media segments 107 that is not otherwise automatically communicated to an aggregation point 124. 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 network entity (including, for example, information indicating which jacks of the devices are connected to which jacks 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 jacks and/or that are not able to communicate such information to the aggregation point 124 (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 point 124). 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 jacks of the devices are connected to which jacks of other devices in the network (for example, other network entities), and information about the physical media attached to the jacks of the devices. This information can be provided to the aggregation point 124, for example, by manually entering such information into a file (such as a spreadsheet) and then uploading the file to the aggregation point 124 (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 point 124 (for example, using a web browser).

The aggregation point 124 can also obtain information about the layout of the building or buildings in which the network is deployed, as well as information indicating where each network entity and physical media segment 107 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 jack 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)).

The aggregation point 124 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.

The aggregation point 124 also includes functionality that provides an interface for external devices or entities to access the physical layer information maintained by the aggregation point 124. This access can include retrieving information from the aggregation point 124 as well as supplying information to the aggregation point 124. In this embodiment, the aggregation point 124 is implemented as “middleware” that is able to provide such external devices and entities with transparent and convenient access to the PLI. Because the aggregation point 124 aggregates PLI from the relevant devices on the IP network 126 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 the IP network 126 that provide PLI, nor do such devices need to have the capacity to respond to requests from such external devices and entities.

The aggregation point 124, in the embodiment shown in FIG. 1, implements an application programming interface (API) by which application-layer functionality can gain access to the physical layer information maintained by the aggregation point 124 using a software development kit (SDK) that describes and documents the API.

Any other portion of the IP network 126 is typically implemented using one or more inter-networking devices. As noted above, an inter-networking device is a type of network entity and can be configured to read PLM information that is stored in or on the segments of physical media 107 that are attached to its jacks and to communicate the PLM information it reads from the attached segments of media 107 (as well as information about the inter-networking device itself) to the aggregation point 124 like any other network entity described here.

The aggregation point 124 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 the aggregation point 124 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, the aggregation point 124 and the network entities are configured so that the aggregation point 124 can automatically discover and connect with the network entities that provide PLI to an aggregation point 124 that are on the network 126. In this way, when network entities that are able to provide PLI to an aggregation point 124 are coupled to the IP network 126, an aggregation point 124 is able to automatically discover the network entities and start aggregating physical layer information for that network entity without requiring the person installing the network entity to have knowledge of the aggregation points 124 that are on the IP network 126. Similarly, when an aggregation point 124 is coupled to the IP network 126, the aggregation point 124 is able to automatically discover and interact with devices that are capable of providing PLI to an aggregation point without requiring the person installing the aggregation point 124 to have knowledge of the devices that are on the IP network 126. Thus, the physical-layer information resources described here can be easily integrated into the IP network 126.

The aggregation point 124 can aggregate the PLI from the network entities and physical communication media to associate jacks of network entities (e.g., patch panels) with physical communication media. For example, the PLI can be used to associate a given jack of a network entity with a give physical communication media and/or a particular connector of the physical communication media. Aggregating the PLI can include aggregating multiple such associations to determine physical layer connections between devices.

More information about physical layer information and the aggregation point 124 can be found in U.S. Provisional Patent Application Ser. No. 61/124,624, filed on Feb. 13, 2009, titled “MANAGED CONNECTIVITY SYSTEMS AND METHODS” and U.S. patent application Ser. No. 12/705,497, filed on Feb. 12, 2010, titled “AGGREGATION OF PHYSICAL LAYER INFORMATION RELATED TO A NETWORK”, both of which are hereby incorporated herein by reference.

The IP network 126 can include one or more local area networks and/or wide area networks (including for example the Internet). As a result, the aggregation point 124 need not be located at the same site as the network entities.

Various conventional IP networking techniques can be used in deploying the system of FIG. 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 in FIG. 1, each network entity, each jack (134, 154) of each network entity, and each media segment 107 is individually addressable. Where IP addresses are used to individually address each network entity, a virtual private network (VPN) dedicated for use with the various network entities can be used to segregate the IP addresses used for the network entities from the main IP address space that is used in the IP network 126.

In the particular embodiment shown in FIG. 1, the system 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 the jacks (134, 154) of the network entities and providing assistance with carrying out moves, adds, and changes. PLI provided by the aggregation point 124 can be used to improve upon conventional “guided MAC” processes. For example, information about the location of the jack (134, 154) and the visual appearance (for example, the color or shape) of the relevant physical media segment 107 (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 the system 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 expected jack (134, 154). 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 the system 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 a particular network entity and/or to a particular jack (134, 154) or by displaying messages on a liquid crystal display (LCD) included on or near the network entity. Other PLM functions include keeping historical logs about the media 107 connected to the network entity.

In addition to network entities, the techniques described here for reading PLM information stored in or on a segment of physical communication media 107 can be used in one or more end user devices 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 PLM information that is stored in or on the segments of physical communication media 107 that are attached to their jacks and to communicate the media information the read from the attached segments of media 107 (as well as information about the devices themselves) to an aggregation point 124 as described here.

In an example, the wall plate devices 130, 150 can communicate PLI with the aggregation point 124 along with “non-service” network traffic over the communication media 107a and 107c respectively. As used herein “non-service” network traffic is defined with respect to the wall plate devices (130, 150), such that network traffic destined for or originating from an end user device (106a, 106c) is “non-service” network traffic. In some examples, the wall plate devices 130, 150 can communicate PLI through a host server 402. In such examples, the host server 402 is communicatively coupled to each of the wall plate devices 130, 150 using appropriate physical communication media 308. The host server 402 can be coupled to the LAN 104 by connecting the host server 402 to a corresponding communication media 308 connected on the other end to a network entity (e.g., patch panel 110). Notably, the physical communication media 308 used for communication with the host server 402 is distinct from the communication media 107 used for “non-service” network traffic. Physical communication media 308, however, can be the same or a different type of communication media as the communication media 107. For example, physical communication media 308 can include CAT-5, 6, and 7 twisted-pair cables, optical cables, or coaxial cable.

The host server 402 can be configured to communicate with the aggregation point 124 over the LAN 104 and, more broadly, the IP network 126. The host server 402 can communicate PLI to/from the aggregation point 124 and also communicate PLI to/from each wall outlet device 130, 150. In this way, the PLI from each wall outlet device 130, 150 can be provided to the aggregation point 124 and the aggregation point 124 can provide information and/or commands to each wall outlet device 130, 150. In some examples, one or more of the wall outlet devices 130, 150 can communicative wirelessly as described in more detail below.

FIG. 2 is a block diagram of one high-level embodiment of a jack 200 and media reading interface 108 that are suitable for use as a jack 134, 154 in a wall pate device 130, 150 of FIG. 1.

Each jack 200 comprises a first attachment point 206 and a second attachment point 208. The first attachment point 206 is used to attach one or more communication paths 210 to the jack 200, and the second attachment point 208 is used to attach a segment of physical communication media 107 to the jack 200. The one or more communication paths 210 can be part of the wall outlet device 130, 150 and connected to appropriate components within the wall outlet device 130, 150 or can be part of another communication media 107 that is connected to another network entity (e.g., patch panel 110) at its other end.

In the particular embodiment shown in FIG. 2, the first attachment point 206 is located near the rear of the jack 200. As a consequence, the first attachment point 206 is also referred to here as the “rear attachment point” 206. Also, in this embodiment, the rear attachment point 206 is configured to attach the one or more communication paths 210 to the jack 200 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 suitable rear attachment points 206 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 in FIG. 2, the second attachment point 208 is located near the front of the jack 200. As a consequence, the second attachment point 208 is also referred to here as the “front attachment point” 208. In the embodiment shown in FIG. 2, the front attachment point 208 for each jack 200 is designed for use with “connectorized” media segments 107 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 a connector 102 at at least one end of the segment. The front attachment point 208 is implemented using a suitable connector or adapter that mates with the corresponding connector 102 on the end of the media segment 107. The connector 102 is used to facilitate the easy and repeated attachment and unattachment of the media segment 107 to the jack 200. 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 attachment point 208 is implemented using compatible modular plugs) or optical cables having SC, LC, FC, LX.5, MTP, or MPO connectors (in which case, the front attachment point 208 is implemented using compatible SC, LC, FC, LX.5, MTP, or MP0 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.

Each jack 200 communicatively couples the respective rear attachment point 206 to the respective front attachment point 208. As a result, one or more communication paths 210 attached to the respective rear attachment point 206 are communicatively coupled to any media segment 107 attached to the respective front attachment point 208. In one implementation, each jack 200 is designed for use with one or more communication paths 107 and a media segment 107 that comprise the same type of communication path(s), in which case each jack 200 communicatively couples the one or more communication paths 210 attached to the respective rear attachment point 206 to any media segment 107 attached to the respective front attachment point 208 at the physical layer level without any media conversion. In other implementations, each jack 200 communicatively couples the one or more communication paths 210 attached to the respective rear attachment point 206 to any media segment 107 attached to the respective front attachment point 208 in other ways (for example, using a media converter if the rear one or more communication paths 210 and the media segment 107 comprise different types of communication paths).

As shown in FIG. 2, the jack 200 is configured for use with media segments 107 that include a PLM interface 216 that, when the corresponding connector 214 is inserted into (or otherwise attached to) a front attachment point 208 of the jack 200, communicatively couples a storage device or other component(s) to a corresponding media reading interface 108 so that the associated programmable processor 106 can obtain PLM information from the storage device or other component(s). In one implementation of the embodiment shown in FIG. 2, each connector 102 itself houses the storage device or other component(s) and the PLM interface can be implemented by incorporating appropriate electrical contacts in the connector 102.

In another implementation of such an embodiment, the storage device and other component(s) are housed within a housing that is separate from the connector 102. In such an implementation, the housing is configured so that it can be snapped onto the media segment 107 or the connector 102, with the PLM interface 216 positioned relative to the connector 102 so that the PLM interface 216 will properly mate with the media reading interface 108 when the connector 102 is inserted into (or otherwise attached to) the front attachment point 208.

Various examples of PLM interfaces are described in United States Patent Publication No. US 2011-0116748, filed Oct. 15, 2010, and titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS AND METHODS THEREOF,” U.S. patent application Ser. No. 13/025,841, filed on Feb. 11, 2011, titled “MANAGED FIBER CONNECTIVITY SYSTEMS,” and U.S. patent application Ser. No. 13/025,750, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS,” U.S. Provisional Patent Application Ser. No. 61/124,624, filed on Feb. 13, 2009, titled “MANAGED CONNECTIVITY SYSTEMS AND METHODS,” and U.S. patent application Ser. No. 12/705,497, filed on Feb. 12, 2010, titled “AGGREGATION OF PHYSICAL LAYER INFORMATION RELATED TO A NETWORK,” all of which are hereby incorporated herein by reference. In some of these examples, a four-line PLM interface is used, where the interface includes a single data line for reading and writing data, a power line for providing power to the storage device, a ground line for providing a ground level, and an extra line reserved for future use. Also, in these examples, a storage device that supports the UNI/O bus protocol is used, where the UNI/O bus protocol is used for communicating over the single data lead. One example of such a storage device and PLM interface are the storage devices and interfaces used in the QUAREO™ family of physical layer management products that are commercially available from TE Connectivity.

FIG. 3 is a diagram illustrating one embodiment of wall outlet 300 that is suitable for use as a wall outlet device 130, 150 in the system 100 of FIG. 1. Wall outlet 300 can have one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 3, the wall outlet 300 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types of jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, the wall outlet 300 terminates a horizontal run of corresponding media 107 (e.g., multi-mode optical cable, CAT-5, CAT-6 cables) for each jack 200. In the implementation illustrated in FIG. 3, the wall outlet 300 is a passive wall outlet 150 such that each jack 200 terminates a horizontal run of a corresponding media 107. In implementations in which wall outlet 300 is a distribution wall outlet 130, the horizontal run of the corresponding media 107 can be terminated at a switch (not shown) in the wall outlet 300. In the implementation shown in FIG. 3, the wall outlet 300 terminates at least one run of a passive optical cable and at least one run of a twisted pair cable (e.g., CAT-5 or CAT-6 cable).

The wall outlet 300 also includes an active module 301 that comprises a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front attachment point 208 of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the host server 402. The programmable processor 302 can also be configured to send PLI regarding itself to the host server 402 as well as receiving information from the host server 402.

To implement the communications with the host server 402, the active module 301 can include a signaling circuit 304, such as an RS-422 signaling circuit, coupled via appropriate pulse transformers 306 to a communication media 308 which is connected at the other end to the host server 402. As such, the signaling circuit 304 can communicate with the host server 402 using a serial communication scheme over the communicate media 308. The active module 301 also includes a power supply unit 310 that is coupled to the transformer 306 for recovering power from the signals on the communication media 308, and for supplying such recovered power to the programmable processor 302 and signaling circuit 304 as described in more detail below. The active module 301 can also include a local input/output port 312 such as a UNIO port. Advantageously, the wall outlet 300 enables the non-service traffic from all of its ports (jacks 200) to travel on paths (e.g., communication media 107) that are distinct from the paths of the service traffic (e.g., communication media 308).

FIG. 4 is an example of the host server 402 communicatively coupled to a plurality of wall outlets 300 via a plurality of communication media 308. The host server 402 can be configured to relay communications between the plurality of wall outlets 300 and the aggregation point 124. The communications between the aggregation point 124 and the host server 402 can be in the form of IP communications sent, for example, via network switch 160 through IP network 126 to the aggregation point 124.

In the example shown in FIG. 4, the host server 402 can include a multiplex module 404 (e.g., a RS-422 MUX) to multiplex/demultiplex signals between the host server 402 and the plurality of wall outlets 300. A programmable processor 406 in the host server 402 can transmit and receive signals from the plurality of wall outlets 300 via the multiplex module 404. The programmable processor 406 can also communicate with the aggregation point 124 via the switch 160 and IP network 126. In an example, the programmable processor 402 in the host server 402 can act as a master and direct control of each slave processor 302 in a wall outlet 300. Accordingly, the master processor 406 can instruct each slave processor 302 to obtain PLM information from communication media 107 connected to jacks 200 of their respective wall outlets 300.

The host server 404 can also include a power interface 408 that can be coupled to a suitable power source 410 (e.g., DC power source). The multiplex module 404 can be coupled to the power interface 408 to simplex power and data over the communication media 308 to each wall outlet 300. That power can be recovered from the communication media 208 by the power supply unit 310 in each wall outlet 300. In other examples, conductors (e.g., a power cable) that are separate from the communication media 108 can be used to provide power to each wall outlet 300.

In an example, each communication media 308 can comprise a CAT-5 or CAT-6 cable and the host server 402 and each wall outlet 300 can implement serial communication (e.g., RS-422) therebetween using 1, 2, or 4 pairs (e.g., twisted pairs) of communication lines.

FIGS. 5 and 6 illustrate an example where 2 twisted pairs in a communication media 308 are used between the host server 402 and a wall outlet 300. With 2 twisted pairs full duplex communication can be implemented with a differential transmission method. Accordingly, transmissions to the wall outlet 300 occur on a first pair and transmissions to the host server 402 occur on a second pair. The host server 402 can include suitable amplifiers 502 for transmitting and receiving signals over the respective twisted pairs. Likewise, the signaling circuit 304 in the wall outlet 300 can also include suitable amplifiers 504 for transmitting and receiving signals over the respective twisted pairs. The host server 402 can also include a first pulse transformer 506 coupled across a first twisted pair used for transmitting signals from the host server 402 to the wall outlet 300. The first pulse transformer 506 can also be coupled to DC power (e.g., from the power interface 408) for providing a DC power average on the first twisted pair. The host server 402 can also include a second pulse transformer 506 for providing DC ground average on the second twisted pair. The wall outlet 300 can include a corresponding first pulse transformer 308 and second pulse transformer 308 for recovering the DC power as a difference between the DC power in the first twisted pair and the DC power in the second twisted pair. This power can be recovered by the power supply unit 310 and provided to the programmable processor 302 and signaling circuit 304. The host server 402 and the wall outlet 300 can also include suitable jacks 510, 512 for connecting of the communication media 108.

FIG. 7 illustrates an example where 1 twisted pair in a communication media 308 is used between the host server 402 and a wall outlet 300. With 1 twisted pair, half duplex communication is implemented using a differential transmission method. Accordingly, transmissions to and from the host server 402 and the wall outlet 300 occur over the same twisted pair. Similar to that described with respect to FIGS. 5 and 6, the host server 402 and the wall outlet 300 include respective amplifiers 702 for transmitting and receiving signals over the twisted pair. In this example, however, the transmit and receive amplifiers 702, 703 are both coupled to the (same) twisted pair. Additionally, a single pulse transformer 704 is used at host server 402 to couple DC power and ground onto the twisted pair. Likewise, a single pulse transformer 705 is used at the wall outlet 300 to recover the DC power from the twisted pair.

FIG. 8 illustrates an example where 4 twisted pairs in a communication media 308 are used between the host server 402 and a wall outlet 300. In this example two of the twisted pairs are used for full duplex communication using (e.g., differential transmission) between the host server 402 and the wall outlet 300. The other two twisted pairs are used to provide DC power from the host server 402 to the wall outlet 300. Accordingly, the transmit and receive amplifiers 802 of the host server 402 are coupled to a first twisted pair and a second twisted pair respectively. Likewise, the transmit and receive amplifiers 803 of the wall outlet 300 are couple to the second twisted pair and the first twisted pair respectively. A first transformer 804 in the host server 402 is coupled to a third twisted pair and DC power to provide DC power on the third twisted pair. A second transformer 805 in the host server 402 is coupled to the fourth twisted pair to provide DC ground over the fourth twisted pair. Likewise, a first and second transformers 806 in the wall outlet 300 are coupled to the third and fourth twisted pair to recover the DC power therefrom.

In Example 2, the wall outlet 900 that is used differs from the wall outlet 300 used in Example 1. The wall outlet 900 that is used in Example 2 is shown in FIG. 9. It is to be understood that, in practice, wall outlet 300 and wall outlet 900 may be used within the same network.

FIG. 9 illustrates another example of a wall outlet 900 that is suitable for use as a wall outlet device 130, 150 in the system 100 of FIG. 1. Wall outlet 900 can include one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 9, the wall outlet 900 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types of jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, the wall outlet 900 terminates a horizontal run of corresponding media 107 (e.g., multi-mode optical cable, CAT-5, CAT-6 cables) for each jack 200. In the implementation illustrated in FIG. 3, the wall outlet 300 is a partially passive wall outlet such that three of the jacks 200 terminate a horizontal run of a corresponding media 107. One horizontal run of corresponding media 107 is terminated at an active module 901 in the wall outlet 300. In the implementation shown in FIG. 9, the wall outlet 900 terminates at least one run of a passive optical cable and at least one run of a twisted pair cable (e.g., CAT-5 or CAT-6 cable).

The active module 901 comprises a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front connector of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the aggregation point 124. The programmable processor 302 can also be configured to send PLI regarding itself to the aggregation point 124 as well as receiving information from the aggregation point 124.

To implement the communications with the aggregation point 124, the programmable processor 302 can be configured to communicate with a switch 902 within the active module 901. The switch 902 can be coupled to the programmable processor 302 and can also be coupled to a jack 200 for connection of physical communication media 107 to an end user device 106 and to another jack 200 for connection of a horizontal run of physical communication media 107 to a network entity (e.g., patch panel 110). Accordingly, the switch 902 can function to relay information between the network entity (e.g., switch 160) and an end user device 106 connected to the jack 200, and between the network entity (e.g., switch 160) and the programmable processor 302. The programmable processor 302 can use this connection with the switch 902 to communicate with the aggregation point 124. For example, the programmable processor 302 can communicate PLI to the switch 902 which can provide the PLI over the network 104 to the aggregation point 124. Advantageously, this configuration enables communication between the aggregation point 124 and the programmable processor 302 to be implemented over the same communication media 107 that are used for “non-service” network traffic. Accordingly, no additional communication media 308 need be run. Moreover, this configuration can be easily retrofit into existing networks due to the lack of additional components required outside of the wall outlet 900. Finally, the wall outlet 900 enables the non-service traffic from all of its ports (jacks 200), except for one (or more) port(s), to travel on paths (e.g., communication medium 107) that are distinct from the paths of the service traffic (e.g., communication mediums 308).

The active module 901 can also includes a power supply unit 310 to recover power from the communication media 107, such as, for example, by power over Ethernet (PoE) for powering of the programmable processor 302 and switch 902. Line power can also be used as an option in non-PoE installations.

FIG. 10 illustrates another example of a wall outlet 1000 that is suitable for use as a wall outlet device 130, 150 in the system 100 of FIG. 1. The wall outlet 1000 is similar to the wall outlet 900 except, here, the communications to the aggregation point 124 are over a communication media 308 that is distinct from the communication media 107 used for “non-service” network traffic.

Wall outlet 1000 can include one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 10, the wall outlet 1000 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types can jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, the wall outlet 1000 terminates a horizontal run of corresponding media 107 (e.g., multi-mode optical cable, CAT-5. CAT-6 cables) for each jack 200. In the implementation illustrated in FIG. 10, the wall outlet 100 is a passive wall outlet 150 such that each jack 200 terminates a horizontal run of a corresponding media 107. In implementations in which wall outlet 1000 is a distribution wall outlet 130, the horizontal run of the corresponding media 107 can be terminated at a switch (not shown) in the wall outlet 1000. In the implementation shown in FIG. 10, the wall outlet 1000 terminates at least one run of a passive optical cable and at least one run of a twisted pair cable (e.g., CAT-5 or CAT-6 cable).

The wall outlet 1000 includes an active module 1001 comprising a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front connector of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the aggregation point 124. The programmable processor 302 can also be configured to send PLI regarding itself to the aggregation point 124 as well as receiving information from the aggregation point 124.

To implement the communications with the aggregation point 124, the programmable processor 302 can be configured to communicate with a media access control/physical layer (MAC/PHY) device 1002 within the wall outlet 100. The MAC/PHY 1002 can be coupled to the programmable processor 302 and can also be coupled to a jack 200 for connection of physical communication media 308 to a network entity (e.g., patch panel 110). Accordingly, the MAC/PHY 1002 can translate and forward information between the programmable processor 302 and the network entity. The programmable processor 302 can use this connection with the MAC/PHY 1002 to communicate with the aggregation point 124. For example, the programmable processor 302 can communicate PLI to the MAC/PHY 1002 which can provide the PLI over the network 104 to the aggregation point 124. Advantageously, the wall outlet 1000 enables the non-service traffic from all of its ports (jacks 200) to travel on paths (e.g., communication media 107) that are distinct from the paths of the service traffic (e.g., communication media 308).

The active module 1001 can also include a power supply unit 310 to recover power from the communication media 308, such as, for example, by power over Ethernet (PoE) for powering of the programmable processor 302 and MAC/PHY 1002. Line power can also be used as an option in non-PoE installations.

FIG. 11 illustrates another example of a wall outlet 1100 that is suitable for use as a wall outlet 130, 150, in the system 100 of FIG. 1. The wall outlet 1100 is similar to the wall outlet 1000 except, here, a switch 1102 in the wall outlet 1100 forms a LAN that is used to connect to multiple (e.g., all) jacks 200 of the wall outlet.

Wall outlet 1100 can include one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 11, the wall outlet 1100 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types of jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, a first jack 200 for the optical cable terminates a horizontal run of the corresponding passive optical cable (e.g., multi-mode optical cable). The wall outlet 1100 also provides a rear jack 200 for connecting to a horizontal run of a CAT-5 or CAT-6 cable to couple the switch 1102 to a network device (e.g., patch panel 110).

The wall outlet 1100 also comprises a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front connector of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the aggregation point 124. The programmable processor 302 can also be configured to send PLI regarding itself to the aggregation point 124 as well as receiving information from the aggregation point 124.

To implement the communications with the aggregation point 124, the programmable processor 302 can be configured to communicate with the switch 1102 within the wall outlet 1100. The switch 1102 can be coupled to the programmable processor 302 and can also be coupled to a plurality of jacks 200 for connection of physical communication media 107 to a plurality of end user devices 106 and to another jack 200 for connection of a horizontal run of physical communication media 107 to a network entity (e.g., patch panel 110). Accordingly, the switch 1102 can function to relay information between the network entity (e.g., patch panel 110, switch 160) and the end user devices 106 connected to the jacks 200. The switch 1102 can also function to relay information between the network entity (e.g., patch panel 110, switch 160) and the programmable processor 302. The programmable processor 302 can use this connection with the switch 1102 to communicate with the aggregation point 124. For example, the programmable processor 302 can communicate PLI to the switch 1102 which can provide the PLI over the network 104 to the aggregation point 124. Advantageously, this configuration enables communication between the aggregation point 124 and the programmable processor 302 to be implemented over the same communication media 107 that are used for “non-service” network traffic. Accordingly, no additional communication media 308 need be run. Moreover, this configuration can be easily retrofit into existing networks due to the lack of additional components required outside of the wall outlet 1100. The wall outlet 1100 also includes a power supply unit 310 to recover power from the communication media 107, such as, for example, by power over Ethernet (PoE) for powering of the programmable processor 302 and switch 1102. Line power can also be used as an option in non-PoE installations.

FIG. 12 illustrates another example of a wall outlet 1200 that is suitable for use as a wall outlet 130, 150, in the system of FIG. 1. The wall outlet 1200 is similar to the wall outlet 1100 except wall outlet 1200 incorporates power over Ethernet (PoE) for one or more of the jacks 200 supported by the switch 1102. Accordingly, each of the components of wall outlet 1200 functions as described with respect to wall outlet 1100. The power supply unit 310 is additionally coupled to one or more of the jacks 200 that are for coupling of communication media 107 to end user devices 106. The power supply unit 310 is configured to provide POE to the one or more jacks 200 in the wall outlet 1200. This configuration may use IEEE 802.3at-2009 PoE+(25.5 W) link over the horizontal run of the communication media 107 to enable sufficient power supply of the PoE to the wall outlet 1200. Line power can also be used as an option for some or all of the PoE provided at the jacks 200 for coupling of communication media 107 to end user devices 106.

FIG. 13 illustrates another example of a wall outlet 1300 that is suitable for use as a wall outlet 130, 150, in the system of FIG. 1. The wall outlet 1300 is similar to the wall outlet 110 except, here, the horizontal run of the communication media 107 is a hybrid cable including both fiber optic and copper wire. Accordingly, each of the components of the wall outlet 1300 functions as described with respect to the wall outlet 1100, except in addition to or instead of sending signals over a CAT-5 or CAT-6 cable, the switch 1102 communicates with an active optical module 1304 to convert between electrical signals for the switch 1102 and optical signals on the fiber optic of the hybrid cable. The copper wire portion of the hybrid cable can be used for power over Ethernet (PoE) to power the programmable processor 302 and the switch 1102. Line power can also be used as an option for non-PoE installations.

The wall outlet 1300 also includes a media access control/physical layer (MAC/PHY) device 1302 coupled between the programmable processor 302 and the switch 1102. The MAC/PHY 1302 can translate and forward information between the programmable processor 302 and the switch 1102. The programmable processor 302 can use this connection with the MAC/PHY 1302 and switch 1102 to communicate with the aggregation point 124. For example, the programmable processor 302 can communicate PLI to the MAC/PHY 1302 which can provide the PLI to the switch 1102 which provides the PLI over the network 104 to the aggregation point 124.

FIG. 14 illustrates another example of a wall outlet 1400 that is suitable for use as a wall outlet 130, 150, in the system of FIG. 1. The wall outlet 1400 is similar to the wall outlet 1300 except, wall outlet 1400 incorporates power over Ethernet (PoE) for one or more of the jacks 200 supported by the switch 1102. Accordingly, each of the components of wall outlet 1400 functions as described with respect to wall outlet 1300. The power supply unit 310 is additionally coupled to one or more of the jacks 200 that are for coupling of communication media 107 to end user devices 106. The power supply unit 310 is configured to provide POE to the one or more jacks 200 in the wall outlet 1300. This configuration may use IEEE 802.3at-2009 PoE+(25.5 W) link over the horizontal run of the communication media 107 to enable sufficient power supply of the PoE to the wall outlet 1400. Line power can also be used as an option for some or all of the PoE provided at the jacks 200 for coupling of communication media 107 to end user devices 106 that is coupled to switch 1102.

FIG. 15 illustrates an example of the connection between a network device 1502 (e.g., switch 160) and a wall outlet 1300, 1400 for either of the Examples 6 or 7 using a hybrid cable 107 described with respect to FIGS. 13 and 14. As shown, a network switch 1504 can be coupled to an active optical module 1506 for communicating optical signals to/from an active optical module 1304 of the wall outlet 1300, 1400 over the optical fiber(s) of the hybrid cable 107. A DC power source 1508 can be coupled to a power interface 1510 to provide DC power (e.g., PoE) over the copper wires of the hybrid cable 107 to the power supply unit 310 of the wall outlet 1300, 1400.

FIG. 16 illustrates another example of a wall outlet 1600 that is suitable for use as a wall outlet device 130, 150 in the system 100 of FIG. 1. Wall outlet 1600 can include one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 16, the wall outlet 1600 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types of jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, the wall outlet 1600 terminates a horizontal run of corresponding media 107 (e.g., multi-mode optical cable, CAT-5. CAT-6 cables) for each jack 200. In the implementation illustrated in FIG. 16, the wall outlet 1600 is a passive wall outlet 150 such that each jack 200 terminates a horizontal run of a corresponding media 107. In implementations in which wall outlet 1600 is a distribution wall outlet 130, the horizontal run of the corresponding media 107 can be terminated at a switch (not shown) in the wall outlet 1600. In the implementation shown in FIG. 16, the wall outlet 1600 terminates at least one run of a passive optical cable and at least one run of a twisted pair cable (e.g., CAT-5 or CAT-6 cable).

The wall outlet 1600 also includes an active module 1601 that comprises a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front connector of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the aggregation point 124. The programmable processor 302 can also be configured to send PLI regarding itself to the aggregation point 124 as well as receiving information from the aggregation point 124.

To implement the communications with the aggregation point 124, the programmable processor 302 can be configured to communicate with a wireless transceiver 1602 in the active module 1601 that is coupled to an antenna 1604. The wireless transceiver 1602 can translate and forward information between the programmable processor 302 and another entity (e.g., a wireless access point) through wireless communications. The wireless transceiver can use any suitable wireless transmission protocol including, but not limited to IEEE 802.11 (WiFi), IEEE 802.14.5 (ZigBee), and Bluetooth. In an implementation of this example, the programmable processor 302 can use this connection with the wireless transceiver 1602 to communicate with the aggregation point 124. For example, the wireless transceiver 1602 can be wirelessly coupled to another device which is coupled to the network 104. Using the wireless transceiver 1602, PLI and other information can be wirelessly transmitted to/from the other device. The device can provide the PLI over the network 104 to the aggregation point 124. In some implementations of this example, the programmable processor 302 is not coupled to the aggregation point 124 in real time, and other device(s) can occasionally wirelessly couple with the wireless transceiver 1602 to obtain/provide PLI from/to the programmable processor 302. The other device(s) can then also occasionally communicatively couple to the aggregation point 124 for synchronizing of PLI.

In some examples, the other device can be another wireless transceiver 1602 in a wall outlet 1600. In one implementation of such an example, multiple wall outlets 1600 can be wirelessly coupled together (e.g., in a mesh network) to provide a communication link from remote wall outlets 1600 to more centralized wall outlets 1600 having a wired connection to network 104 or a communication link to another wireless device (e.g., wireless access point) having a wired connection to network 104. In some such implementations, the centralized wall outlets can have a communicative coupling with the aggregation point 124, thereby providing communicative coupling between the aggregation point 124 and the remote wall outlets 1600. In some such implementations, the centralized wall outlet(s) can include, in addition to including a wireless transceiver 1602 and antenna 1602, a wired communicative coupling with the network 104 and/or aggregation point 124 as described in any of the Examples 1-7 in FIGS. 1-15 above. Such centralized wall outlet(s) can forward PLI between the aggregation point 124 and the remote wall outlet(s) 1600. In this way, the remote wall outlets 1600 can be communicatively coupled to the aggregation point 124 via wireless coupling with a centralized wall outlet(s).

Advantageously, the wall outlet 1600 enables the non-service traffic from all of its ports (jacks 200) to travel on paths (e.g., communication media 107) that are distinct from the paths of the service traffic (e.g., wireless signals).

In an example, the active module 1601 includes a power supply unit 310 to obtain power from a line power source 1606. The power supply unit 310 can also optionally provide PoE to one or more of the jacks 200. In an alternative example, the power supply unit 310 can include power harvesting circuits to harvest power from wireless signals sensed by the antenna 1604. In any case, the power supply unit 310 can provide power for the programmable processor 302 and the wireless transceiver 1602. The active module 1601 can also include a local input/output port 312 such as a UNIO port.

FIG. 17 illustrates another example of a wall outlet 1700 that is suitable for use as a wall outlet device 130, 150 in the system 100 of FIG. 1. Wall outlet 1700 can include one or more jacks 200 configured to mate with one or more connectors of one or more physical communication media 107. In the example shown in FIG. 17, the wall outlet 1700 includes one jack 200 for mating with an optical cable and three jacks 200 for mating with a CAT-5 or CAT-6 cable, however other numbers and types of jacks can be used. In addition to being configured to mate with a corresponding connector of a communication media 107, the wall outlet 1700 terminates a horizontal run of corresponding media 107 (e.g., multi-mode optical cable, CAT-5, CAT-6 cables) for each jack 200. In the implementation illustrated in FIG. 17, the wall outlet 1700 is a passive wall outlet 150 such that each jack 200 terminates a horizontal run of a corresponding media 107. In implementations in which wall outlet 1700 is a distribution wall outlet 130, the horizontal run of the corresponding media 107 can be terminated at a switch (not shown) in the wall outlet 1700. In the implementation shown in FIG. 17, the wall outlet 1700 terminates at least one run of a passive optical cable and at least one run of a twisted pair cable (e.g., CAT-5 or CAT-6 cable).

The wall outlet 1700 also includes an active module 1701 that comprises a programmable processor 302 that is coupled to a storage device. The programmable processor 302 can include any suitable programmable processor, such as a microprocessor (e.g., an 8-bit microprocessor). The storage device can include, for example, an Electrically Erasable Programmable Read-Only Memory (EEPROM) or other non-volatile memory device. The programmable processor 302 and the storage device can be the same die, on separate dies, or can be incorporated into a chip scale package.

The programmable processor 302 can be configured to communicate with a storage device or other component in a communication media 107 connected to a jack 200 over a media reading interface 108 of the respective jack 200. The media reading interface 108, while the corresponding connector is inserted into a front connector of a jack 200, communicatively couples the programmable processor 302 to the corresponding PLM interface 216 so that the programmable processor 302 can access the storage device or other entity associated with the connector of the communication media 107.

The programmable processor 302 is configured to obtain PLM information from communication media 107 connected (mated) with jacks 200 and send the PLM information to the aggregation point 124. The programmable processor 302 can also be configured to send PLI regarding itself to another device as well as receiving information from another device.

To implement the communications with the other device, the programmable processor 302 can be configured to communicate with a radio frequency identification (RFID) transceiver 1702 in the active module 1701 that is coupled to an antenna 1704. The programmable processor 302 can write information to the non-volatile memory (e.g., EEPROM) of the RFID transceiver 1704. When the RFID transceiver 1702 is interrogated by a RFID reader, the RFID transceiver 1702 can provide such PLI to the RFID reader. A device and/or user associated with the RFID reader may then provide such PLI to the aggregation point 124 for synchronizing of PLI. The RFID transceiver 1702 can be either an active or a passive RFID transceiver.

Advantageously, the wall outlet 1700 enables the non-service traffic from all of its ports (jacks 200) to travel on paths (e.g., communication media 107) that are distinct from the paths of the service traffic (e.g., RFID signals).

The active module 1701 also includes a power supply unit 310 to obtain power from a battery 1706 therein for powering of the programmable processor 302. In some implementations, the battery 1706 can be separate from any battery used to power (e.g., temporarily store) energy for the RFID transceiver 1702. In other implementations, the battery 1706 can also supply power to the RFID transceiver 1702 and be re-charged by the RFID transceiver 1702. In some implementations, the power supply unit 310 can include power harvesting circuits to harvest power from “non-RFID” wireless signals (as well as signals from an RFID reader interrogating the RFID transceiver 1702) sensed by the antenna 1704 to re-charge the battery 1706. The active module 1701 can also include a local input/output port 312 such as a UNIO port.

It should be understood that, in practice, wall outlet 300, wall outlet 900, wall outlet 1000, wall outlet 1100, wall outlet 1200, wall outlet 1300, wall outlet 1400, wall outlet 1600, and/or wall outlet 1700 may be used within the same network. Additionally, although not specifically shown in the Figures herein, any of the Examples described above including a rear jack 200 for mating with a connector of a horizontal run of a communication media 107, can include a media reading interface 108 in that rear jack 200 as described with respect to FIG. 2. Such media reading interface 108 can be coupled to the programmable processor 302 included in the wall outlet for obtaining and providing PLM information therefrom to the aggregation point 124 as described above.

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement, which is calculated to achieve the same purpose, may be substituted for the specific embodiments shown. Therefore, it is manifestly intended that this invention be limited only by the claims and the equivalents thereof.

Further details, embodiments, and implementations can be found in the following United States patent applications, all of which are hereby incorporated herein by reference:

U.S. Provisional Patent Application Ser. No. 61/124,624, filed on Feb. 13, 2009, titled “MANAGED CONNECTIVITY SYSTEMS AND METHODS” (also referred to here as the “'624 Application”); U.S. patent application Ser. No. 12/705,497, filed on Feb. 12, 2010, titled “AGGREGATION OF PHYSICAL LAYER INFORMATION RELATED TO A NETWORK” (is also referred to here as the '497 Application); U.S. patent application Ser. No. 12/705,501, filed on Feb. 12, 2010, titled “INTER-NETWORKING DEVICES FOR USE WITH PHYSICAL LAYER INFORMATION” (also referred to here as the '501 Application); U.S. patent application Ser. No. 12/705,506, filed on Feb. 12, 2010, titled “NETWORK MANAGEMENT SYSTEMS FOR USE WITH PHYSICAL LAYER INFORMATION” (also referred to here as the '506 Application); U.S. patent application Ser. No. 12/705,514, filed on Feb. 12, 2010, titled “MANAGED CONNECTIVITY DEVICES, SYSTEMS, AND METHODS” (also referred to here as the '514 Application); 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”); 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”); 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”); U.S. Provisional Patent Application Ser. No. 61/252,964, filed on Oct. 19, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY”, Attorney Docket No. 02316.3045USP1; U.S. Provisional Patent Application Ser. No. 61/253,208, filed on Oct. 20, 2009, titled “ELECTRICAL PLUG FOR MANAGED CONNECTIVITY”, Attorney Docket No. 02316.3045USP2; U.S. patent application Ser. No. 12/907,724, filed on Oct. 19, 2010, titled “MANAGED ELECTRICAL CONNECTIVITY SYSTEMS”, Attorney Docket No. 02316.3045USU1; U.S. Provisional Patent Application Ser. No. 61/303,948, filed on Feb. 12, 2010, titled “PANEL INCLUDING BLADE FEATURE FOR MANAGED CONNECTIVITY”, Attorney Docket No. 02316.3069USP1; U.S. Provisional Patent Application Ser. No. 61/413,844, filed on Nov. 15, 2010, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USP2; U.S. Provisional Patent Application Ser. No. 61/439,693, filed on Feb. 4, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USP3; U.S. patent application Ser. No. 13/025,730, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USU1; U.S. patent application Ser. No. 13/025,737, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USU2; U.S. patent application Ser. No. 13/025,743, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USU3; U.S. patent application Ser. No. 13/025,750, filed on Feb. 11, 2011, titled “COMMUNICATIONS BLADED PANEL SYSTEMS”, Attorney Docket No. 02316.3069USU4; U.S. Provisional Patent Application Ser. No. 61/303,961; filed on Feb. 12, 2010, titled “Fiber Plug And Adapter For Managed Connectivity”, Attorney Docket No. 02316.3071USP1; U.S. Provisional Patent Application Ser. No. 61/413,828, filed on Nov. 15, 2010, titled “Fiber Plugs And Adapters For Managed Connectivity”, Attorney Docket No. 02316.3071USP2; U.S. Provisional Patent Application Ser. No. 61/437,504, filed on Jan. 28, 2011, titled “Fiber Plugs And Adapters For Managed Connectivity”, Attorney Docket No. 02316.3071USP3; U.S. patent application Ser. No. 13/025,784, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”, Attorney Docket No. 02316.3071USU1; U.S. patent application Ser. No. 13/025,788, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”, Attorney Docket No 02316.3071USU2; U.S. patent application Ser. No. 13/025,797, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”, Attorney Docket No. 02316.3071USU3; U.S. patent application Ser. No. 13/025,841, filed on Feb. 11, 2011, titled “Managed Fiber Connectivity Systems”, Attorney Docket No. 02316.3071USU4; U.S. Provisional Patent Application Ser. No. 61/413,856, filed on Nov. 15, 2010, titled “CABLE MANAGEMENT IN RACK SYSTEMS”, Attorney Docket No. 02316.3090USP1; U.S. Provisional Patent Application Ser. No. 61/466,696, filed on Mar. 23, 2011, titled “CABLE MANAGEMENT IN RACK SYSTEMS”, Attorney Docket No. 02316.3090USP2; U.S. Provisional Patent Application Ser. No. 61/252,395, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS”, Attorney Docket No. 02316.3021USP1; U.S. patent application Ser. No. 12/905,689, filed on Oct. 15, 2010, titled “MANAGED CONNECTIVITY IN ELECTRICAL SYSTEMS”, Attorney Docket No. 02316.3021USU1; U.S. Provisional Patent Application Ser. No. 61/252,386, filed on Oct. 16, 2009, titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS”, Attorney Docket No. 02316.3020USP1; U.S. patent application Ser. No. 12/905,658, filed on Oct. 15, 2010, titled “MANAGED CONNECTIVITY IN FIBER OPTIC SYSTEMS”, Attorney Docket No. 02316.3020USU1; U.S. Provisional Patent Application Ser. No. 61/467,715, filed on Mar. 25, 2011, titled “DOUBLE-BUFFER INSERTION COUNT STORED IN A DEVICE ATTACHED TO A PHYSICAL LAYER MEDIUM”, Attorney Docket No. 100.1176USPR; U.S. Provisional Patent Application Ser. No. 61/467,725, filed on Mar. 25, 2011, titled “DYNAMICALLY DETECTING A DEFECTIVE CONNECTOR AT A JACK”, Attorney Docket No. 100.1177USPR; U.S. Provisional Patent Application Ser. No. 61/467,729, filed on Mar. 25, 2011, titled “IDENTIFIER ENCODING SCHEME FOR USE WITH MULTI-PATH CONNECTORS”, Attorney Docket No. 100.1178USPR; U.S. Provisional Patent Application Ser. No. 61/467,736, filed on Mar. 25, 2011, titled “SYSTEMS AND METHODS FOR UTILIZING VARIABLE LENGTH DATA FIELD STORAGE SCHEMES ON PHYSICAL COMMUNICATION MEDIA SEGMENTS”, Attorney Docket No. 100.1179USPR; and U.S. Provisional Patent Application Ser. No. 61/467,743, filed on Mar. 25, 2011, titled “EVENT-MONITORING IN A SYSTEM FOR AUTOMATICALLY OBTAINING AND MANAGING PHYSICAL LAYER INFORMATION USING A RELIABLE PACKET-BASED COMMUNICATION PROTOCOL”, Attorney Docket No. 100.1181USPR.