In communications infrastructure installations, a variety of communications devices can be used for switching, cross-connecting, and interconnecting communications signal transmission paths in a communications network. Some such communications devices are installed in one or more equipment racks to permit organized, high-density installations to be achieved in limited space available for equipment.
Communications devices can be organized into communications networks, which 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.
Network management systems (NMS) are typically aware of logical communication links that exist in a communications network, but typically do not have information about the specific physical layer media (e.g., the communications devices, cables, couplers, etc.) 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.
The present disclosure relates to communications connector assemblies and arrangements that provide physical layer management (PLM) capabilities.
The accompanying drawings, which are incorporated in and constitute a part of the description, illustrate several aspects of the present disclosure. A brief description of the drawings is as follows:
The communications network 101 includes interconnected network components (e.g., connector assemblies, inter-networking devices, internet working devices, servers, outlets, and end user equipment (e.g., computers)). In one example implementation, communications signals S1 pass from a computer to a wall outlet to a port of communication panel, to a first port of an inter-networking device, out another port of the inter-networking device, to a port of the same or another communications panel, to a rack mounted server.
The portion of the communications network 101 shown in
The at least one port 132 of the first connector assembly 130 may be directly connected to a port 132′ of the second connector assembly 130′. As the term is used herein, the port 132 is directly connected to the port 132′ when the communications signals S1 pass between the two ports 132, 132′ without passing through an intermediate port. For example, routing a patchcord between port 132 and port 132′ directly connects the ports 132, 132′.
The port 132 of the first connector assembly 130 also may be indirectly connected to the port 132′ of the second connector assembly 130′. As the term is used herein, the port 132 is indirectly connected to the port 132′ when the communications signals S1 pass through an intermediate port when traveling between the ports 132, 132′. For example, in one implementation, the communications signals S1 may be routed over one media segment from the port 132 at the first connector assembly 130 to a port of a third connector assembly at which the media segment is coupled to another media segment that is routed from the port of the third connector assembly to the port 132′ of the second connector assembly 130′.
Non-limiting examples of media segments include optical fibers, which carry optical data signals, and electrical conductors (e.g., CAT-5, 6, and 7 twisted-pair cables), which carry electrical data signals. Media segments also can include electrical plugs, fiber optic connectors (e.g., SC, LC, FC, LX.5, or MPO connectors), adapters, media converters, and other physical components terminating to the fibers, conductors, or other such media segments. The techniques described here also can be used with other types of connectors including, for example, BNC connectors, F connectors, DSX jacks and plugs, bantam jacks and plugs.
In the example shown, each media segment 105, 115 is terminated at a plug or connector 110, 120, respectively, which is configured to communicatively connect the media segments 105, 115. For example, in one implementation, the port 132 of the connector assembly 130 can be configured to align ferrules of two fiber optic connectors 110, 120. In another implementation, the port 132 of the connector assembly 130 can be configured to electrically connect an electrical plug with an electrical socket (e.g., a jack). In yet another implementation, the port 132 can include a media converter configured to connect an optical fiber to an electrical conductor.
In accordance with some aspects, the connector assembly 130 does not actively manage (e.g., is passive with respect to) the communications signals S1 passing through port 132. For example, in some implementations, the connector assembly 130 does not modify the communications signal S1 carried over the media segments 105, 115. Further, in some implementations, the connector assembly 130 does not read, store, or analyze the communications signal S1 carried over the media segments 105, 115.
In accordance with aspects of the disclosure, the communications and data management system 100 also provides physical layer information (PLI) functionality as well as physical layer management (PLM) functionality. As the term is used herein, “PLI functionality” refers to the ability of a physical component or system to identify or otherwise associate physical layer information with some or all of the physical components used to implement the physical layer of the system. As the term is used herein, “PLM functionality” refers to the ability of a component or system to manipulate or to enable others to manipulate the physical components used to implement the physical layer of the system (e.g., to track what is connected to each component, to trace connections that are made using the components, or to provide visual indications to a user at a selected component).
As the term is used herein, “physical layer information” refers to information about the identity, attributes, and/or status of the physical components used to implement the physical layer of the communications system 101. In accordance with some aspects, physical layer information of the communications system 101 can include media information, device information, and location information.
As the term is used herein, “media information” refers to physical layer information pertaining to cables, plugs, connectors, and other such media segments. In accordance with some aspects, the media information is stored on or in the media segments, themselves. In accordance with other aspects, the media information can be stored at one or more data repositories for the communications system, either alternatively or in addition to the media, themselves. Non-limiting examples of media information include a part number, a serial number, a plug or other connector type, a conductor or fiber type, a cable or fiber length, cable polarity, a cable or fiber pass-through capacity, a date of manufacture, a manufacturing lot number, information about one or more visual attributes of physical communication media (e.g., information about the color or shape of the physical communication media or an image of the physical communication media), and an insertion count (i.e., a record of the number of times the media segment has been connected to another media segment or network component). Media information also can include testing or media quality or performance information. 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.
As the term is used herein, “device information” refers to physical layer information pertaining to the communications panels, inter-networking devices, media converters, computers, servers, wall outlets, and other physical communications devices to which the media segments attach. In accordance with some aspects, the device information is stored on or in the devices, themselves. In accordance with other aspects, the device information can be stored at one or more data repositories for the communications system, either alternatively or in addition to the devices, themselves. Non-limiting examples of device information include a device identifier, a device type, port priority data (that associates a priority level with each port), and port updates (described in more detail herein).
As the term is used herein, “location information” refers to physical layer information pertaining to a physical layout of a building or buildings in which the network 101 is deployed. Location information also can include information indicating where each communications device, media segment, network component, or other component that is physically located within the building. In accordance with some aspects, the location information of each system component is stored on or in the respective component. In accordance with other aspects, the location information can be stored at one or more data repositories for the communications system, either alternatively or in addition to the system components, themselves.
In accordance with some aspects, one or more of the components of the communications network 101 is configured to store physical layer information pertaining to the component as will be disclosed in more detail herein. In
In another example implementation, the media segments 105, 115 or connectors 110, 120 may store media information that includes a count of the number of times that the media segment (or connector) has been inserted into port 132. In such an example, the count stored in or on the media segment is updated each time the segment (or plug or connector) is inserted into port 132. This insertion count value can be used, for example, for warranty purposes (e.g., to determine if the connector has been inserted more than the number of times specified in the warranty) or for security purposes (e.g., to detect unauthorized insertions of the physical communication media).
In accordance with certain aspects, one or more of the components of the communications network 101 also can read the physical layer information from one or more media segments retained thereat. In certain implementations, one or more network components includes a media reading interface that is configured to read physical layer information stored on or in the media segments or connectors attached thereto. For example, in one implementation, the connector assembly 130 includes a media reading interface 134 that can read media information stored on the media cables 105, 115 retained within the port 132. In another implementation, the media reading interface 134 can read media information stored on the connectors or plugs 110, 120 terminating the cables 105, 115, respectively.
In some implementations, some types of physical layer information can be obtained by the connector assembly 130 from a user at the connector assembly 130 via a user interface (e.g., a keypad, a scanner, a touch screen, buttons, etc.). The connector assembly 130 can provide the physical layer information obtained from the user to other devices or systems that are coupled to the network 101 (as described in more detail herein). In other implementations, some or all physical layer information can be obtained by the connector assembly 130 from other devices or systems that are coupled to the network 101. For example, physical layer information pertaining to media that is not configured to store such information can be entered manually into another device or system that is coupled to the network 101 (e.g., at the connector assembly 130, at the computer 160, or at the aggregation point 150).
In some implementations, some types of non-physical layer information (e.g., network information) can be obtained by one network component from other devices or systems that are coupled to the network 101. For example, the connector assembly 130 may pull non-physical layer information from one or more components of the network 101. In other implementations, the non-physical layer information can be obtained by the connector assembly 130 from a user at the connector assembly 130.
In accordance with some aspects of the disclosure, the physical layer information read by a network component may be processed or stored at the component. For example, in certain implementations, the first connector assembly 130 shown in
In some implementations, the connector assembly 130 is configured to add, delete, and/or change the physical layer information stored in or on the segment of physical communication media 105, 115 (i.e., or the associated connectors 110, 120). For example, in some implementations, the media information stored in or on the segment of physical communication media 105, 115 can be updated to include the results of testing that is performed when a segment of physical media is installed or otherwise checked. In other implementations, such testing information is supplied to the aggregation point 150 for storage and/or processing. In some implementations, modification of the physical layer information does not affect the communications signals S1 passing through the connector assembly 130.
In other implementations, the physical layer information obtained by the media reading interface (e.g., interface 134 of
The physical layer information is communicated over the network 101 just like any other data that is communicated over the network 101, while at the same time not affecting the communication signals S1 that pass through the connector assembly 130 on the normal ports 132. Indeed, in some implementations, the physical layer information may be communicated as one or more of the communication signals S1 that pass through the normal ports 132 of the connector assemblies 130, 130′. For example, in one implementation, a media segment may be routed between the PLI port 136 and one of the “normal” ports 132. In such an implementation, the physical layer information may be passed along the communications network 101 to other components of the communications network 101 (e.g., to the one or more aggregation points 150 and/or to the one or more computer systems 160). By using the network 101 to communicate physical layer information pertaining to it, an entirely separate network need not be provided and maintained in order to communicate such physical layer information.
In other implementations, however, the communications network 101 includes a data network along which the physical layer information described above is communicated. At least some of the media segments and other components of the data network may be separate from those of the communications network 101 to which such physical layer information pertains. For example, in some implementations, the first connector assembly 130 may include a plurality of fiber optic adapters defining ports at which connectorized optical fibers are optically coupled together to create an optical path for communications signals S1. The first connector assembly 130 also may include one or more electrical cable ports at which the physical layer information (see PLI signals S2) are passed to other parts of the data network. (e.g., to the one or more aggregation points 150 and/or to the one or more computer systems 160).
Each connector assembly 202 includes one or more ports 204, each of which is used to connect two or more segments of physical communication media to one another (e.g., to implement a portion of a logical communication link for communication signals S1 of
In the particular implementation shown in
In the particular implementation shown in
In the second type of connector assembly configuration 212, a group of connector assemblies 202 are physically located near each other (e.g., in a bay or equipment closet). Each of the connector assemblies 202 in the group includes its own respective programmable processor 206. However, in the second connector assembly configuration 212, some of the connector assemblies 202 (referred to here as “interfaced connector assemblies”) include their own respective network interfaces 216 while some of the connector assemblies 202 (referred to here as “non-interfaced connector assemblies”) do not. The non-interfaced connector assemblies 202 are communicatively coupled to one or more of the interfaced connector assemblies 202 in the group via local connections. In this way, the non-interfaced connector assemblies 202 are communicatively coupled to the IP network 218 via the network interface 216 included in one or more of the interfaced connector assemblies 202 in the group. In the second type of connector assembly configuration 212, the total number of network interfaces 216 used to couple the connector assemblies 202 to the IP network 218 can be reduced. Moreover, in the particular implementation shown in
In the third type of connector assembly configuration 214, a group of connector assemblies 202 are physically located near each other (e.g., within a bay or equipment closet). Some of the connector assemblies 202 in the group (also referred to here as “master” connector assemblies 202) include both their own programmable processors 206 and network interfaces 216, while some of the connector assemblies 202 (also referred to here as “slave” connector assemblies 202) do not include their own programmable processors 206 or network interfaces 216. Each of the slave connector assemblies 202 is communicatively coupled to one or more of the master connector assemblies 202 in the group via one or more local connections. The programmable processor 206 in each of the master connector assemblies 202 is able to carry out the PLM functions for both the master connector assembly 202 of which it is a part and any slave connector assemblies 202 to which the master connector assembly 202 is connected via the local connections. As a result, the cost associated with the slave connector assemblies 202 can be reduced. In the particular implementation shown in
Each programmable processor 206 is configured to execute software or firmware that causes the programmable processor 206 to carry out various functions described below. Each programmable processor 206 also includes suitable memory (not shown) that is coupled to the programmable processor 206 for storing program instructions and data. In general, the programmable processor 206 determines if a physical communication media segment is attached to a port 204 with which that processor 206 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 associated media reading interface 208.
In the fourth type of connector assembly configuration 215, a group of connector assemblies 202 are housed within a common chassis or other enclosure. Each of the connector assemblies 202 in the configuration 215 includes their own programmable processors 206. In the context of this configuration 215, the programmable processors 206 in each of the connector assemblies are “slave” processors 206. Each of the slave programmable processor 206 is also communicatively coupled to a common “master” programmable processor 217 (e.g., over a backplane included in the chassis or enclosure). The master programmable processor 217 is coupled to a network interface 216 that is used to communicatively couple the master programmable processor 217 to the IP network 218.
In this configuration 215, each slave programmable processor 206 is configured to determine if physical communication media segments are attached to its port 204 and to read the physical layer 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 interfaces 208. The physical layer information is communicated from the slave programmable processor 206 in each of the connector assemblies 202 in the chassis to the master processor 217. The master processor 217 is configured to handle the processing associated with communicating the physical layer information read from by the slave processors 206 to devices that are coupled to the IP network 218.
The system 200 includes functionality that enables the physical layer information that the connector assemblies 202 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 implementation shown in
The aggregation point 220 includes functionality that obtains physical layer information from the connector assemblies 202 (and other devices) and stores the physical layer information in a data store. The aggregation point 220 can be used to receive physical layer information from various types of connector assemblies 202 that have functionality for automatically reading information stored in or on the segment of physical communication media. Also, the aggregation point 220 and aggregation functionality 224 can 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 (e.g., 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 220 also can be used to obtain other types of physical layer information. For example, in this implementation, the aggregation point 220 also obtains information about physical communication media segments that is not otherwise automatically communicated to an aggregation point 220. This information can be provided to the aggregation point 220, for example, by manually entering such information into a file (e.g., a spreadsheet) and then uploading the file to the aggregation point 220 (e.g., 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 220 (e.g., using a web browser).
The aggregation point 220 also includes functionality that provides an interface for external devices or entities to access the physical layer information maintained by the aggregation point 220. This access can include retrieving information from the aggregation point 220 as well as supplying information to the aggregation point 220. In this implementation, the aggregation point 220 is implemented as “middleware” that is able to provide such external devices and entities with transparent and convenient access to the PLI maintained by the access point 220. Because the aggregation point 220 aggregates PLI from the relevant devices on the IP network 218 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 218 that provide PLI, nor do such devices need to have the capacity to respond to requests from such external devices and entities.
For example, as shown in
As shown in
In the example shown in
The aggregation point 220 can be implemented on a standalone network node (e.g., a standalone computer running appropriate software) or can be integrated along with other network functionality (e.g., integrated with an element management system or network management system or other network server or network element). Moreover, the functionality of the aggregation point 220 can be distribute across many nodes and devices in the network and/or implemented, for example, in a hierarchical manner (e.g., with many levels of aggregation points). The IP network 218 can include one or more local area networks and/or wide area networks (e.g., the Internet). As a result, the aggregation point 220, NMS 230, and computer 236 need not be located at the same site as each other or at the same site as the connector assemblies 202 or the inter-networking devices 238.
Also, power can be supplied to the connector assemblies 202 using conventional “Power over Ethernet” techniques specified in the IEEE 802.3af standard, which is hereby incorporated herein by reference. In such an implementation, a power hub 242 or other power supplying device (located near or incorporated into an inter-networking device that is coupled to each connector assembly 202) 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 each connector assembly 202 to the associated inter-networking device.
Each electrical segment 305 of the connector arrangement 310 carries communication signals (e.g., communications signals S1 of
The connector assembly 320 is electrically coupled to one or more printed circuit boards. For example, the connector assembly 320 can support or enclose a first printed circuit board 326, which connects to insulation displacement contacts (IDCs) 327 or to another type of electrical contacts. The IDCs 327 terminate the electrical segments 329 of physical communications media (e.g., conductive wires). The first printed circuit board 326 manages the primary communication signals carried from the conductors terminating the cable 305 to the electrical segments 329 that couple to the IDCs 327.
In accordance with some aspects, the connector arrangement 310 can include a storage device 315 configured to store physical layer information. The connector arrangement 310 also includes second contact members 314 that are electrically coupled (i.e., or otherwise communicatively coupled) to the storage device 315. In one implementation, the storage device 315 is implemented using an EEPROM (e.g., a PCB surface-mount EEPROM). In other implementations, the storage device 315 is implemented using other non-volatile memory device. Each storage device 315 is arranged and configured so that it does not interfere or interact with the communications signals communicated over the media segment 305.
The connector assembly 320 also includes a second contact arrangement (e.g., a media reading interface) 324. In certain implementations, the media reading interface 324 is accessible through the socket port 325. The second contact arrangement 324 is aligned with and configured to interface with the second contact members 314 of the media segment to receive the physical layer information from the storage device 315 when the connector arrangement 310 is inserted into the socket 325 of the connector assembly 320.
In some such implementations, the storage device interfaces 314 and the media reading interfaces 324 each comprise three (3) leads—a power lead, a ground lead, and a data lead. The three leads of the storage device interface 314 come into electrical contact with three (3) corresponding leads of the media reading interface 324 when the corresponding media segment is inserted in the corresponding port 325. In certain example implementations, a two-line interface is used with a simple charge pump. In still other implementations, additional leads can be provided (e.g., for potential future applications). Accordingly, the storage device interfaces 314 and the media reading interfaces 324 may each include four (4) leads, five (5) leads, six (6) leads, etc.
The storage device 315 also may include a processor or micro-controller, in addition to the storage for the physical layer information. In some example implementations, the micro-controller can be used to execute software or firmware that, for example, performs an integrity test on the cable 305 (e.g., by performing a capacitance or impedance test on the sheathing or insulator that surrounds the cable 305, (which may include a metallic foil or metallic filler for such purposes)). In the event that a problem with the integrity of the cable 305 is detected, the micro-controller can communicate that fact to a programmable processor (e.g., processor 206 of
The connector assembly 320 also can support or enclose a second printed circuit board 328, which connects to the second contact arrangement 324. The second printed circuit board 328 manages the physical layer information communicated from a storage device 315 through second contacts 314, 324. In the example shown, the second printed circuit board 328 is positioned on an opposite side of the connector assembly 320 from the first printed circuit board 326. In other implementations, the printed circuit boards 326, 328 can be positioned on the same side or on different sides. In one implementation, the second printed circuit board 328 is positioned horizontally relative to the connector assembly 320 (see
The second printed circuit board 328 can be communicatively connected to one or more programmable electronic processors and/or one or more network interfaces. In one implementation, one or more such processors and interfaces can be arranged as components on the printed circuit board 328. In another implementation, one of more such processor and interfaces can be arranged on a separate circuit board that is coupled to the second printed circuit board 328. For example, the second printed circuit board 328 can couple to other circuit boards via a card edge type connection, a connector-to-connector type connection, a cable connection, etc. The network interface is configured to send the physical layer information to the data network (e.g., see signals S2 of
In accordance with one aspect, the connector arrangement 3000 includes an RJ plug 3002 that connects to the end of an electrical segment of communications media, such as twisted pair copper cable. The socket 3106 of the connector assembly 3100 defines an RJ jack (e.g., an RJ-45 jack). In the example shown, the RJ plug 3002 is insertable into a port of a mating RJ jack 3106 in the patch panel 3102 of the connector assembly 3100 as will be described below. In accordance with other aspects, however, the connector arrangement 3000 and connector assembly 3100 can define other types of electrical connections.
In the example shown, the plug 3002 includes a plug nose body 3004 for holding main signal contacts 3012, which are electrically connected to segments of communications media terminated at the plug 3002. For example, the main contacts 3012 may be connected to twisted pair conductors of a communications cable. In one implementation, the main signal contacts 3012 are arranged at a front end 3014 of the plug 3002. The main signal contacts 3012 are positioned to electrically connect to contacts positioned in the jack 3106 for signal transmission.
The plug 3002 further includes a finger tab 3050, which facilitates latching the connector arrangement 3000 to the connector assembly 3100. The finger tab 3050 includes a latch surface 3052 for latching to the connector assembly 3100. In some implementations, the finger tab 3050 extends from the plug nose body 3004.
Certain types of plugs 3002 also include a keying structure 3015 that is shaped to mate with a keyway 3065 defined in the connector assembly 3100. In certain implementations, the keying structure 3015 is formed at a base of the finger tab 3050. Certain types of plugs 3002 also include wire managers 3008 for managing the electrical segments of communications media (e.g., twisted wire pairs) and a strain relief boot 3010 which snaps to the plug nose body 3004.
The plug 3002 also includes a plug cover 3006 that mounts on the plug nose body 3004 (see
The connector arrangement 3000 also includes a storage device 3030 (
In one implementation, the connector arrangement 3000 also can include a communications device 3036 that is configured to send and receive communications signals to and from a local source. For example, the communications device 3036 can include an IR transceiver. Such a communications device 3036 can enable a technician to read and/or write data to the storage device 3030 using an infra-red wand or probe (e.g., a handheld wand or probe). Accordingly, the technician can access information stored on the connector arrangement 3000 without plugging the connector arrangement 3000 into a port of connector assembly 3100.
In some implementations, the storage device 3030 can be arranged on a circuit 3020 (
In the example shown in
In accordance with some aspects, the circuit 3020 is a flexible circuit that defines a base portion 3038 and an extending portion 3040. The MOSFET 3032, the EEPROM 3034, and the IR device 3036 can be mounted to the base portion 3038. The circuit contacts 3026 can be arranged on the extending portion 3040. In some implementations, the extending portion 3040 is located within the keying structure 3015. In certain implementations, the extending portion 3040 is located on the finger tab 3050. The circuit contacts 3026 permit connection of the EEPROM 3034 to a media reading interface 3188 of the connector assembly 3100 as will be disclosed herein.
In the example shown, the flexible circuit 3020 is positioned along an outer surface 3042 of plug nose body 3004. In the example shown, the extending portion is positioned on the same side of the plug as the finger tab 3050. The base portion 3038 of the flexible circuit 3020 is positioned along a periphery of surface 3042. Extending portion 3040 is positioned over a flexible rib 3046 of plug nose body 3004. Rib 3046 supports flexible circuit 3020 in the area of extending portion 3040 so that contacts 3026 are positioned to engage the media reading interface 3188 associated with the connector assembly 3100. Rib 3046 includes retainer pegs 3058 for engaging holes 3060 on extending portion 3040 of the flexible circuit 3020 for retention.
Referring now to
The connector assembly 3100 also includes a media reading interface 3188 (
In the example shown, the patch panel 3102 includes circuitry 3180 (
The main PCB 3182 includes a main communications interface connector 3184 and jack interface connectors 3186 (see
The main PCB 3182 also defines holes 3210 (
The frame 3120 includes a main portion 3122 and ends 3124, 3126. Each end 3124, 3126 of the frame 3120 includes holes 3128 to mount frame 3120 to a rack. The main portion 3122 of the frame 3120 includes upper and lower flanges 3140. Tabs 3142 on the flanges 3140 cooperate with a complementary mating structure on the fascia 3160 to connect the fascia 3160 to the frame 3120 (see
The main portion 3122 of the frame 3120 defines one or more openings 3132 configured to receive the jack modules 3106. Frame 3120 also defines a second aperture 3134 (
In certain implementations, each opening 3162 of the front panel 3160 defines a keyway 3165 shaped to receive the keying structure 3015 of the connector arrangement 3000. In the example shown in
In general, the media reading interfaces 3188 align with the openings 3162 of the front panel 3160. In certain implementations, the media reading interfaces 3188 are positioned adjacent the keyways 3165 (e.g., see
In accordance with one aspect, the connector arrangement 4000 includes an RJ plug 4002 that connects to the end of an electrical segment of communications media, such as twisted pair copper cable (not shown). In the example shown, the RJ plug 4002 is insertable into a port of a mating RJ jack (e.g., an RJ-45 jack) 4106 in the patch panel 4102 of the connector assembly 4100 as will be described below (see
In the example shown, the plug 4002 includes a plug nose body 4004 (
The plug 4002 also includes a plug cover 4006 that mounts on the plug nose body 4004 (see
The plug 4002 also includes a wire manager 4008 for managing the twisted wire pairs and a strain relief boot 4010, which snaps to the plug nose body 4004 (see
The connector arrangement 4000 also includes a storage device 4030 (
In one implementation, the connector arrangement 4000 also can include a communications device (not shown) that is configured to send and receive communications signals to and from a local source. For example, the communications device can include an IR transceiver. Such a communications device can enable a technician to read and/or write data to the storage device 4030 using an infra-red wand or probe (e.g., a handheld wand or probe). Accordingly, the technician can access information stored on the connector arrangement 4000 without unplugging the connector arrangement 4000 from a port of connector assembly 4100.
In some implementations, the storage device 4030 can be arranged on a circuit 4020 (
In the example shown in
In accordance with some aspects, the circuit 4020 is an FR-4 PCB 4022 defining a U-shaped body having a base 4024 and legs 4026. The MOSFET 4032 and the EEPROM 4034 can be mounted to the base 4024 of the PCB 4022. The circuit contacts are arranged on the legs 4026 of the PCB 4022. The circuit contacts permit connection of the EEPROM 4034 to a media reading interface 4188 of the connector assembly 4100 as will be disclosed herein. In one example, contacts of the media reading interface 4188 can extend through the slotted openings 4009 to connect to the circuit contacts.
Referring now to
The connector assembly 4100 also includes a media reading interface 4188 (
In the example shown, the patch panel 4102 includes internal circuitry 4180 (
Storage interface connectors 4186 form the media reading interface 4188 for connector assembly 4100. In the example shown in
In certain implementations, a microswitch 4224 can be mounted to the PCB 4182 adjacent to each storage interface connector 4182 for sensing the presence of a connector arrangement 4000 inserted into the corresponding jack 4106. In the example shown, the microswitch 4224 extends downwardly from the PCB 4182 between the two groups of contacts 4190 (see
In certain implementations, the PCB 4182 also includes an LED indicator 4216 adjacent each storage interface connector 4186 of the PCB 4182 (see
The frame 4120 includes a main portion 4122 and ends 4124, 4126. Each end 4124, 4126 of the frame 4120 defines holes 4128 to mount frame 4120 to a rack. The main portion 4122 of the frame 4120 includes upper and lower flanges 4140. The main portion 4122 defines one or more openings 4132 configured to receive the jack modules 4106. Frame 4120 also defines a second aperture 4134 (
The fascia 4160 is coupled to the frame 4120 to secure the PCB 4182 therebetween. The fascia 4160 defines opening 4162 (
In certain implementations, the fascia 4160 can be formed in multiple pieces. In the example shown, the fascia 4160 includes an upper piece 4161 and a lower portion 4171. The upper and lower pieces 4161, 4171 cooperate to define openings 4162. In the example shown, the upper piece 4161 includes legs 4166 extending downwardly from a main portion 4165 to define slots 4167 (
The upper piece 4161 of the fascia 4160 also includes flanges 4168, which protrude inwardly from either end of the main portion 4165. The flanges 4168 are separated sufficiently to accommodate the communications interface connector 4184 (see
In the example shown, the connector assembly 4100 is assembled by mounting the PCB 4182 to the upper piece 4161 of the fascia 4160 to form a first unit. Locator holes 4212 (
The lower piece 4171 of the fascia 4160 mounts to the frame 4120 to form a second unit (see
The first unit is removably coupled to the second unit (see
Because the first unit includes only the upper fascia 4161, the first unit can be removed from the second unit without disturbing the jack modules 4106 and modular plugs 4002 mounted to the second unit. Accordingly, the PCB 4182 can be replaced by replacing the upper piece 4161 of the fascia 4160 without unplugging the plug modules 4002 from the jack modules 4106.
Once connected, information can be read from media storage device 4030 of the connector arrangement 4000 by a CPU card 4300 connected to main communications interface connector 4184 (see
A number of implementations of the invention defined by the following claims have been described. Nevertheless, it will be understood that various modifications to the described implementations may be made without departing from the spirit and scope of the claimed invention. Accordingly, other implementations are within the scope of the following claims.
This application is a continuation of application Ser. No. 15/707,518, filed Sep. 18, 2017, now U.S. Pat. No. 9,967,983, issued May 8, 2018, which is a continuation of application Ser. No. 15/195,533, filed Jun. 28, 2016, now U.S. Pat. No. 9,769,939, issued Sep. 19, 2017, which is a continuation of application Ser. No. 14/656,801, filed Mar. 13, 2015, now U.S. Pat. No. 9,401,552, issued Jul. 26, 2016, which is a continuation of application Ser. No. 12/905,689, filed Oct. 15, 2010, now U.S. Pat. No. 8,992,260, issued Mar. 31, 2015, which application claims the benefit of provisional application Ser. No. 61/252,395, filed Oct. 16, 2009, and titled “Managed Connectivity in Electrical Systems and Methods Thereof,” which applications are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3243761 | Piorunneck | Mar 1966 | A |
4127317 | Tyree | Nov 1978 | A |
4679879 | Triner et al. | Jul 1987 | A |
4684245 | Goldring | Aug 1987 | A |
4953194 | Hansen et al. | Aug 1990 | A |
4968929 | Hauck et al. | Nov 1990 | A |
4978310 | Shichida | Dec 1990 | A |
5052940 | Bengal | Oct 1991 | A |
5107532 | Hansen et al. | Apr 1992 | A |
5161988 | Krupka | Nov 1992 | A |
5166970 | Ward | Nov 1992 | A |
5222164 | Bass, Sr. et al. | Jun 1993 | A |
5265187 | Morin et al. | Nov 1993 | A |
5305405 | Emmons et al. | Apr 1994 | A |
5353367 | Czosnowski et al. | Oct 1994 | A |
5393249 | Morgenstern et al. | Feb 1995 | A |
5394503 | Dietz, Jr. et al. | Feb 1995 | A |
5413494 | Dewey et al. | May 1995 | A |
5415570 | Sarkissian | May 1995 | A |
5418334 | Williams | May 1995 | A |
5419717 | Abendschein et al. | May 1995 | A |
5448675 | Leone et al. | Sep 1995 | A |
5467062 | Burroughs et al. | Nov 1995 | A |
5470251 | Sano | Nov 1995 | A |
5473715 | Schofield et al. | Dec 1995 | A |
5483467 | Krupka et al. | Jan 1996 | A |
5492478 | White | Feb 1996 | A |
5660567 | Nierlich et al. | Aug 1997 | A |
5674085 | Davis et al. | Oct 1997 | A |
5684871 | Devon | Nov 1997 | A |
5685741 | Dewey et al. | Nov 1997 | A |
5712942 | Jennings et al. | Jan 1998 | A |
5764043 | Czosnowski et al. | Jun 1998 | A |
5800192 | David et al. | Sep 1998 | A |
5821510 | Cohen et al. | Oct 1998 | A |
5854824 | Bengal et al. | Dec 1998 | A |
5871368 | Erdner et al. | Feb 1999 | A |
5910776 | Black | Jun 1999 | A |
6002331 | Laor | Dec 1999 | A |
6079996 | Arnett | Jun 2000 | A |
6095837 | David et al. | Aug 2000 | A |
6095851 | Laity et al. | Aug 2000 | A |
6116961 | Henneberger et al. | Sep 2000 | A |
6222908 | Bartolutti et al. | Apr 2001 | B1 |
6222975 | Gilbert et al. | Apr 2001 | B1 |
6227911 | Boutros et al. | May 2001 | B1 |
6234830 | Ensz et al. | May 2001 | B1 |
6238235 | Shavit et al. | May 2001 | B1 |
6280231 | Nicholls | Aug 2001 | B1 |
6285293 | German et al. | Sep 2001 | B1 |
6300877 | Schannach et al. | Oct 2001 | B1 |
6330148 | Won et al. | Dec 2001 | B1 |
6330307 | Bloch et al. | Dec 2001 | B1 |
6350148 | Bartolutti et al. | Feb 2002 | B1 |
6358093 | Phommachanh et al. | Mar 2002 | B1 |
6364694 | Lien | Apr 2002 | B1 |
6421322 | Koziy et al. | Jul 2002 | B1 |
6422895 | Lien | Jul 2002 | B1 |
6424710 | Bartolutti et al. | Jul 2002 | B1 |
6456768 | Boncek | Sep 2002 | B1 |
D466479 | Pein et al. | Dec 2002 | S |
6499861 | German et al. | Dec 2002 | B1 |
6511231 | Lampert et al. | Jan 2003 | B2 |
6522737 | Bartolutti et al. | Feb 2003 | B1 |
6554484 | Lampert | Apr 2003 | B2 |
6574586 | David et al. | Jun 2003 | B1 |
6612856 | McCormack | Sep 2003 | B1 |
6626697 | Martin et al. | Sep 2003 | B1 |
6636152 | Schannach et al. | Oct 2003 | B2 |
6684179 | David | Jan 2004 | B1 |
6725177 | David et al. | Apr 2004 | B2 |
6743044 | Musolf et al. | Jun 2004 | B2 |
6793408 | Levy et al. | Sep 2004 | B2 |
6802735 | Pepe et al. | Oct 2004 | B2 |
6808116 | Eslambolchi et al. | Oct 2004 | B1 |
6811446 | Chang | Nov 2004 | B1 |
6814624 | Clark et al. | Nov 2004 | B2 |
6837738 | Chen | Jan 2005 | B1 |
6847856 | Bohannon | Jan 2005 | B1 |
6850685 | Tinucci et al. | Feb 2005 | B2 |
6890197 | Liebenow | May 2005 | B2 |
6898368 | Colombo et al. | May 2005 | B2 |
6905363 | Musolf et al. | Jun 2005 | B2 |
6932517 | Swayze et al. | Aug 2005 | B2 |
D510068 | Haggay et al. | Sep 2005 | S |
6939168 | Oleynick et al. | Sep 2005 | B2 |
6961675 | David | Nov 2005 | B2 |
6968994 | Smith | Nov 2005 | B1 |
6971895 | Sago et al. | Dec 2005 | B2 |
6976867 | Navarro et al. | Dec 2005 | B2 |
7033227 | Karir | Apr 2006 | B2 |
7077710 | Haggay et al. | Jul 2006 | B2 |
7081808 | Colombo et al. | Jul 2006 | B2 |
7112090 | Caveney et al. | Sep 2006 | B2 |
7123810 | Parrish | Oct 2006 | B2 |
7153142 | Shifris et al. | Dec 2006 | B2 |
7165728 | Durrant et al. | Jan 2007 | B2 |
7193422 | Velleca et al. | Mar 2007 | B2 |
7207819 | Chen | Apr 2007 | B2 |
7210858 | Sago et al. | May 2007 | B2 |
7226217 | Benton et al. | Jun 2007 | B1 |
7234944 | Nordin et al. | Jun 2007 | B2 |
7241157 | Zhuang et al. | Jul 2007 | B2 |
7297018 | Caveney et al. | Nov 2007 | B2 |
7312715 | Shalts et al. | Dec 2007 | B2 |
D559186 | Kelmer | Jan 2008 | S |
7315224 | Gurovich et al. | Jan 2008 | B2 |
7352285 | Sakama et al. | Apr 2008 | B2 |
7352289 | Harris | Apr 2008 | B1 |
7370106 | Caveney | May 2008 | B2 |
7374101 | Kaneko | May 2008 | B2 |
7384300 | Salgado et al. | Jun 2008 | B1 |
7396245 | Huang et al. | Jul 2008 | B2 |
7479032 | Hoath et al. | Jan 2009 | B2 |
7481681 | Caveney et al. | Jan 2009 | B2 |
7497709 | Zhang | Mar 2009 | B1 |
7519000 | Caveney et al. | Apr 2009 | B2 |
7534137 | Caveney et al. | May 2009 | B2 |
7552872 | Tokita et al. | Jun 2009 | B2 |
7559805 | Yi et al. | Jul 2009 | B1 |
7563116 | Wang | Jul 2009 | B2 |
7570861 | Smrha et al. | Aug 2009 | B2 |
7575454 | Aoki et al. | Aug 2009 | B1 |
7588470 | Li et al. | Sep 2009 | B2 |
7591667 | Navarro et al. | Sep 2009 | B2 |
7605707 | German et al. | Oct 2009 | B2 |
7607926 | Wang | Oct 2009 | B2 |
7635280 | Crumlin et al. | Dec 2009 | B1 |
7648377 | Naito et al. | Jan 2010 | B2 |
7682174 | Chen | Mar 2010 | B2 |
7722370 | Chin | May 2010 | B2 |
7727026 | Qin et al. | Jun 2010 | B2 |
7753717 | Belopolsky et al. | Jul 2010 | B2 |
7785154 | Peng | Aug 2010 | B2 |
7798832 | Qin et al. | Sep 2010 | B2 |
7811119 | Caveney et al. | Oct 2010 | B2 |
7814240 | Salgado et al. | Oct 2010 | B2 |
7867017 | Chen | Jan 2011 | B1 |
7869426 | Hough et al. | Jan 2011 | B2 |
7872738 | Abbott | Jan 2011 | B2 |
7880475 | Crumlin et al. | Feb 2011 | B2 |
7934022 | Velleca et al. | Apr 2011 | B2 |
8157582 | Frey et al. | Apr 2012 | B2 |
8272892 | McNeely et al. | Sep 2012 | B2 |
8282425 | Bopp et al. | Oct 2012 | B2 |
8287316 | Pepe et al. | Oct 2012 | B2 |
8449318 | Beller et al. | May 2013 | B2 |
8992260 | Coffey | Mar 2015 | B2 |
9401552 | Coffey et al. | Jul 2016 | B2 |
9967983 | Coffey et al. | May 2018 | B2 |
20020008613 | Nathan et al. | Jan 2002 | A1 |
20040052498 | Colombo et al. | Mar 2004 | A1 |
20040240807 | Frohlich et al. | Dec 2004 | A1 |
20050153603 | AbuGhazaleh | Jul 2005 | A1 |
20060148279 | German et al. | Jul 2006 | A1 |
20060160395 | Macauley et al. | Jul 2006 | A1 |
20070105453 | Caveney | May 2007 | A1 |
20070237470 | Aronson et al. | Oct 2007 | A1 |
20070254529 | Pepe | Nov 2007 | A1 |
20080090454 | Hoath et al. | Apr 2008 | A1 |
20080096438 | Clark et al. | Apr 2008 | A1 |
20080100467 | Downie et al. | May 2008 | A1 |
20080280483 | Curtis | Nov 2008 | A1 |
20080286987 | Timmins et al. | Nov 2008 | A1 |
20090097846 | Kozischek et al. | Apr 2009 | A1 |
20090098763 | Below et al. | Apr 2009 | A1 |
20090148106 | Moore et al. | Jun 2009 | A1 |
20090166404 | German et al. | Jul 2009 | A1 |
20090215310 | Hoath et al. | Aug 2009 | A1 |
20090232455 | Nhep | Sep 2009 | A1 |
20090238521 | Oba | Sep 2009 | A1 |
20100048064 | Peng | Feb 2010 | A1 |
20100055971 | Craig et al. | Mar 2010 | A1 |
20100057944 | Eberhard | Mar 2010 | A1 |
20100098425 | Kewitsch | Apr 2010 | A1 |
20100211664 | Raza et al. | Aug 2010 | A1 |
20100211665 | Raza et al. | Aug 2010 | A1 |
20100211697 | Raza et al. | Aug 2010 | A1 |
20100215049 | Raza et al. | Aug 2010 | A1 |
20100267274 | McNally et al. | Oct 2010 | A1 |
20110256767 | Malstrom et al. | Oct 2011 | A1 |
20120003877 | Bareel et al. | Jan 2012 | A1 |
20120021636 | Debenedictis et al. | Jan 2012 | A1 |
20120146660 | Mattson | Jun 2012 | A1 |
20120184141 | Mattson | Jul 2012 | A1 |
20140094059 | Pepe et al. | Apr 2014 | A1 |
Number | Date | Country |
---|---|---|
2 499 803 | Apr 2004 | CA |
102 44 304 | Mar 2004 | DE |
10 2004 033 940 | Feb 2006 | DE |
2 236 398 | Apr 1991 | GB |
WO 0065696 | Nov 2000 | WO |
WO 0247215 | Jun 2002 | WO |
WO 2010001400 | Jan 2010 | WO |
WO 2010081186 | Jul 2010 | WO |
WO 2010121639 | Oct 2010 | WO |
Entry |
---|
Avaya's Enhanced SYSTIMAX® iPatch System Enables IT Managers to Optimise Network Efficiency and Cut Downtime, Press Release, May 9, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030509 on Jan. 7, 2009. |
Avaya's Enhanced SYSTIMAX® iPatch System Enables IT Managers to Optimise Network Efficiency and Cut Downtime, Press Release, May 20, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030520 on Jan. 7, 2009. |
European Search Report for Application No. 16182721.7 dated Sep. 22, 2016. |
Intelligent patching systems carving out a ‘large’ niche, Cabling Installation & Maintenance, vol. 12, Issue 7, Jul. 2004 (5 pages). |
intelliMAC: The intelligent way to make Moves, Adds or Changes! NORDX/CDT © 2003 (6 pages). |
International Search Report and Written Opinion dated Jan. 12, 2011. |
ITRACS Physical Layer Manager Faq, obtained on Jun. 11, 2008 from http://www.itracs.com/products/physical-layer-manager-faqs.mtml (6pages). |
Meredith, L., “Managers missing point of intelligent patching,” Daa Center News, Jun. 21, 2005, obtained Dec. 2, 2008 from http://searchdatacenter.techtarget.com/news/article/0,289142,sid80_gci1099991,00.html. |
Ohtsuki, F. et al., “Design of Optical Connectors with ID Modules,” Electronics and Communications in Japan, Part 1, vol. 77, No. 2, pp. 94-105 (Feb. 1994). |
SYSTIMAX® iPatch System Wins Platinum Network of the Year Award, Press Release, Jan. 30, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030130a on Jan. 7, 2009. |
TrueNet; TFP Series Rack Mount Fiber Panels, Spec Sheet; May 2008; 8 pages. |
Number | Date | Country | |
---|---|---|---|
20180332723 A1 | Nov 2018 | US |
Number | Date | Country | |
---|---|---|---|
61252395 | Oct 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15707518 | Sep 2017 | US |
Child | 15972656 | US | |
Parent | 15195533 | Jun 2016 | US |
Child | 15707518 | US | |
Parent | 14656801 | Mar 2015 | US |
Child | 15195533 | US | |
Parent | 12905689 | Oct 2010 | US |
Child | 14656801 | US |