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 connector arrangements that provide physical layer management capabilities. In accordance with certain aspects, the disclosure relates to fiber optic connector assemblies and connector arrangements.
One aspect of the present disclosure relates to a communications panel systems and methods including one or more connector arrangements and connector assemblies implemented as LC-type fiber optic connections.
Another aspect of the present disclosure relates to a communications panel systems and methods including one or more connector arrangements and connector assemblies implemented as MPO-type fiber optic connections.
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:
4-14 illustrate a first example implementation of a connector system that can be utilized on a connector assembly having PLI functionality as well as PLM functionality in accordance with aspects of the present disclosure;
Reference will now be made in detail to exemplary aspects of the present disclosure that are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
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. In other implementations, the communications signals S1 may follow other paths within the communications network 101.
The portion of the communications network 101 shown in
In the example shown, the first connector assembly 130 defines at least one port 132 configured to communicatively couple at least a first media segment (e.g., cable) 105 to at least a second media segment (e.g., cable) 115 to enable the communication signals S1 to pass between the media segments 105, 115. 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, plugging a first terminated end of a patch cable into the port 132 and a second terminated end of the patch cable into the 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 cables, electrical cables, and hybrid cables. The media segments may be terminated with electrical plugs, electrical jacks, fiber optic connectors, fiber optic adapters, media converters, or other termination components. 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 physical media. In accordance with some aspects, the media information is stored on or in the physical media, 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. In accordance with still other aspects, the device information can be stored in the media segments attached thereto. 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 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 are 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).
One or more of the components of the communications network 101 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 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
The physical layer information obtained by the media reading interface may be communicated (see PLI signals S2) over the network 101 for processing and/or storage. In accordance with some aspects, the communications network 101 includes a data network (e.g., see network 218 of
In other implementations, however, the physical layer information may be communicated over the communications network 101 just like any other signal, 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 another implementation, the media segment may be routed between the PLI port 136 and a “normal” port of another connector assembly. In such implementations, the physical layer information may be passed along the communications network 101 to other components of the communications network 101 (e.g., to another connector assembly, to one or more aggregation points 150 and/or to one or more computer systems 160). By using the network 101 to communicate physical layer information pertaining to it, an entirely separate data network need not be provided and maintained in order to communicate such physical layer information.
For example, in the implementation shown in
In some implementations, some types of physical layer information pertaining to media segments 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.). For example, physical layer information pertaining to media that is not configured to store such information can be entered manually into the connector assembly 130 by the user. In certain implementations, the connector assembly 130 can provide the physical layer information obtained from the user to other devices or systems that are coupled to the communications network 101 and/or a separate data network.
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 communications network 101 and/or a separate data network. 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 (e.g., at the connector assembly 130, at the computer 160, or at the aggregation point 150) that is coupled to the network 101 and/or a separate data network.
In some implementations, some types of non-physical layer information (e.g., network information) also can be obtained by one network component (e.g., a connector assembly 130, an aggregation point 150, or a computer 160) from other devices or systems that are coupled to the communications network 101 and/or a separate data network. 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 some implementations, the connector assembly 130 is configured to modify (e.g., 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. The modification of the physical layer information does not affect the communications signals S1 passing through the connector assembly 130.
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
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 some implementations, each of the ports 204 of the connector assemblies 202 comprises a respective media reading interface 208 via which the respective programmable processor 206 is able to determine if a physical communication media segment is attached to that port 204 and, if one is, to read the physical layer information stored in or on the attached segment (if such media information is stored therein or thereon). In other implementations, a single media reading interface 208 may correspond to two or more ports 204. The programmable processor 206 associated with each connector assembly 202 is communicatively coupled to each of the media reading interfaces 208 using a suitable bus or other interconnect (not 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 rack, rack system, 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 rack, rack system, 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
In the fourth type of connector assembly configuration 215, a group of connector assemblies (e.g., distribution modules) 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 the connector assemblies 202 are “slave” processors 206. Each of the slave programmable processors 206 in the group is 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 the fourth configuration 215, each slave programmable processor 206 is configured to manage the media reading interfaces 208 to determine if physical communication media segments are attached to the 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). 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.
In accordance with some aspects, the communications management system 200 includes functionality that enables the physical layer information captured by the connector assemblies 202 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. For example, 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 power cables (e.g., a power wire included in a copper twisted-pair cable) used to connect each connector assembly 202 to the IP network 218.
A first example segment of optical physical communication media includes a first optical fiber 1822 terminated by a first connector arrangement 1820. A second example segment of optical physical communication media includes a second optical fiber 1832 terminated by a second connector arrangement 1830. The first connector arrangement 1820 is plugged into the first port end 1812 and the second connector arrangement 1830 is plugged into the second port end 1814. Each fiber connector arrangement 1820, 1830 includes a ferrule 1824, 1834 through which optical signals from the optical fiber 1822, 1832, respectively, pass.
The ferrules 1824, 1834 of the connector arrangements 1820, 1830 are aligned by the sleeve 1803 when the connector arrangements 1820, 1830 are inserted into the connection opening 1811 of the adapter 1810. Aligning the ferrules 1824, 1834 provides optical coupling between the optical fibers 1822, 1832. In some implementations, each segment of optical physical communication media (e.g., each optical fiber 1822, 1832) carries communication signals (e.g., communications signals S1 of
In some implementations, the first connector arrangement 1820 may include a storage device 1825 that is configured to store physical layer information (e.g., an identifier and/or attribute information) pertaining to the segment of physical communications media (e.g., the first connector arrangement 1820 and/or the fiber optic cable 1822 terminated thereby). In some implementations, the connector arrangement 1830 also includes a storage device 1835 that is configured to store information (e.g., an identifier and/or attribute information) pertaining to the second connector arrangement 1830 and/or the second optic cable 1832 terminated thereby.
In one implementation, each of the storage devices 1825, 1835 is implemented using an EEPROM (e.g., a PCB surface-mount EEPROM). In other implementations, the storage devices 1825, 1835 are implemented using other non-volatile memory device. Each storage device 1825, 1835 is arranged and configured so that it does not interfere or interact with the communications signals communicated over the media segments 1822, 1832.
In accordance with some aspects, the adapter 1810 is coupled to at least a first media reading interface 1816. In certain implementations, the adapter 1810 also is coupled to at least a second media interface 1818. In some implementations, the adapter 1810 is coupled to multiple media reading interfaces. In certain implementations, the adapter 1810 includes a media reading interface for each port end defined by the adapter 1810. In other implementations, the adapter 1810 includes a media reading interface for each connection opening 1811 defined by the adapter 1810. In still other implementations, the adapter 1810 includes a media reading interface for each connector arrangement that the adapter 1810 is configured to receive. In still other implementations, the adapter 1810 includes a media reading interface for only a portion of the connector arrangement that the adapter 1810 is configured to receive.
In some implementations, at least the first media reading interface 1816 is mounted to a printed circuit board 1815. In the example shown, the first media reading interface 1816 of the printed circuit board 1815 is associated with the first port end 1812 of the adapter 1810. In some implementations, the printed circuit board 1815 also can include the second media reading interface 1818. In one such implementation, the second media reading interface 1818 is associated with the second port end 1814 of the adapter 1810.
The printed circuit board 1815 of the connector assembly 1810 can be communicatively connected to one or more programmable processors (e.g., processors 216 of
When the first connector arrangement 1820 is received in the first port end 1812 of the adapter 1810, the first media reading interface 1816 is configured to enable reading (e.g., by the processor) of the information stored in the storage device 1825. The information read from the first connector arrangement 1820 can be transferred through the printed circuit board 1815 to a physical layer management network, e.g., network 101 of
In some such implementations, the storage devices 1825, 1835 and the media reading interfaces 1816, 1818 each comprise three (3) leads—a power lead, a ground lead, and a data lead. The three leads of the storage devices 1825, 1835 come into electrical contact with three (3) corresponding leads of the media reading interfaces 1816, 1818 when the corresponding media segment is inserted in the corresponding port. 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 devices 1825, 1835 and the media reading interfaces 1816, 1818 may each include four (4) leads, five (5) leads, six (6) leads, etc.
The connector system 1000 includes at least one example communications coupler assembly 1200 that can be mounted to a connector assembly, such as a communications panel. One or more example connector arrangements 1100, which terminate segments 1010 of communications media, are configured to communicatively couple to other segments of physical communications media at the coupler assembly 1200 (
In accordance with some aspects, each connector arrangement 1100 is configured to terminate a single segment of physical communications media. For example, each connector arrangement 1100 can include a single connector housing 1110 that terminates a single optical fiber or a single electrical conductor. In one example implementation, each connector arrangement 1100 includes a single LC-type fiber optic connector 1110 that terminates a single optical fiber. In accordance with other aspects, each connector arrangement 1100 includes two or more connector housings 1110, each of which terminates a single segment of physical communications media. For example, a duplex connector arrangement 1100 may include two connector housings 1110, each of which terminates an optical fiber 1010. In other implementations, the connector housings 1110 can be an SC-type, an ST-type, an FC-type, an LX.5-type, etc.
In accordance with still other aspects, each connector arrangement 1100 can include one or more connector housings, each of which terminates a plurality of physical media segments. In one example implementation, each connector arrangement includes a single MPO-type fiber optic connector that terminates multiple optical fibers. In still other systems, other types of connector arrangements (e.g., electrical connector arrangements) can be secured to the communications coupler assembly 1200 or to a different type of connector assembly.
In the example shown in
Each connector arrangement 1100 is configured to store physical layer information. For example, the physical layer information can be stored on or in the body 1111 of one or more of the fiber optic connectors 1110. In the example shown, physical layer information is stored on only one fiber optic connector 1110 of the connector arrangement 1100. In other implementations, however, physical layer information can be stored on each fiber optic connector 1110.
One example storage device 1130 includes a printed circuit board 1131 on which memory circuitry can be arranged. In one example implementation, the storage device 1130 includes an EEPROM circuit arranged on the printed circuit board 1131. In other embodiments, however, the storage device 1130 can include any suitable type of memory. In the example shown in
Electrical contacts 1132 are arranged on the visible side of the printed circuit board 1131 in
In the example in
In the example shown in
In the example shown, the clip 1150 has a monolithic body 1151 defining two channels 1152 separated by an interior wall 1156. Lugs 1157 are positioned on the inner surfaces of the exterior walls of the body 1151 and on both sides of the interior wall 1156. The lugs 1157 are configured to engage cavities/depressions 1117 defined in the fiber optic connector bodies 1111 to secure the connector bodies 1111 within the clip body 1151.
The example adapter housing 1210 shown in
In the example shown in
The fiber optic adapter 1210 includes one or more media reading interfaces 1230, each configured to acquire the physical layer information from the storage device 1130 of a fiber optic connector 1110 plugged into the fiber optic adapter 1210. For example, in one implementation, the adapter 1210 can include a media reading interface 1230 associated with each passage 1215. In another implementation, the adapter 1210 can include a media reading interface 1230 associated with each connection end of each passage 1215. In still other implementations, the adapter 1210 can include a media reading interface 1230 associated with each set of ports that accommodates a connector arrangement 1100.
For example, the quadruplex adapter 1210 shown in
In general, each media reading interface 1230 is formed from one or more contact members 1231 (
One example type of contact member 1231 is shown in
Each contact member 1231 defines at least three moveable contact locations 1233, 1235, and 1236. The flexibility of the contact surfaces 1233, 1235, and 1236 provides tolerance for differences in spacing between the contact member 1231 and the respective printed circuit board 1220 when the coupler assembly 1200 is manufactured. Certain types of contact members 1231 also include at least one stationary contact 1237.
In some implementations, the contact members 1231 of a single media reading interface 1230 are positioned in a staggered configuration to facilitate access to the contact pads 1132 on the connector storage device 1130 of a connector arrangement 1100. For example, as shown in
In some implementations, the contact members 1231 of a single media reading interface 1230 are staggered to facilitate access to the contact pads 1132 on the connector storage device 1130. For example, as shown in
In the example shown in
In the example shown in
The example contact member 1231 shown includes a base 1232 that is configured to be positioned within a slot 1214 defined by an adapter 1210. The base 1232 of certain types of contact members 1231 is configured to secure (e.g., snap-fit, latch, pressure-fit, etc.) to the adapter 1210. The base 1232 also can include a retention section 1238 that secures the member 1231 in the adapter body 1210 (e.g., see
A stationary contact location 1237 may extend from the base 1232, through the slot 1214, toward the printed circuit board 1220 to touch a contact pad or a grounding line on the printed circuit board 1220. A first arm extends from the base 1232 to define the first contact location 1233. A second arm extends from the base 1232 to define a resilient section 1234, the second contact location 1235, and the third contact location 1236. The first and second arms extend generally away from the passage 1215 and toward an exterior of the adapter housing 1210 at the first and third contact locations 1233, 1236 (see
At least the first moveable contact location 1233 is aligned and configured to extend outwardly of the adapter housing 1210 through the slots 1214 to touch a first contact pad on the corresponding circuit board 1220 when the printed circuit board 1220 is mounted to the adapter housing 1210. The ability of the first arm to flex relative to the stationary contact 1237 provides tolerance for placement of the contact member 1231 relative to the circuit board 1220. In certain implementations, the first moveable contact location 1233 touches the same contact pad as the stationary contact location 1237. In one implementation, the stationary contact location 1237 and the first moveable contact location 1233 provide grounding of the contact member 1231.
The second arm extends from the base 1232 to define the resilient section 1234, the second moveable contact location 1235, and the third moveable contact location 1236. In one implementation, the second contact location 1235 defines a trough located on the second arm between the resilient section 1234 and the third contact location 1236. The resilient section 1234 is configured to bias the second contact location 1235 towards the channel passage 1215 (see
The third contact location 1236 is configured to be positioned initially within the passage 1215. For example, the resilient section 1234 biases the third contact section 1236 away from an exterior of the housing 1210 when a fiber optic connector 1110 is not inserted into the passage 1215. The resilient section 1234 is configured to bias the third contact location 1236 through the slot 1214 to an exterior of the housing 1210 when a connector arrangement 1100 or other media segment pushes against the second contact location 1235. In the example shown, the resilient section 1234 is implemented as a looped/bent section of the second arm. In other implementations, the second arm can otherwise include springs, reduced width sections, or portions formed from more resilient materials. In other implementations, other types of contact members can be utilized.
In accordance with some aspects, insertion of the connector body 1111 into the passage 1215 causes the third contact location 1236 to contact the printed circuit board 1220. For example, in some implementations, the key 1115 of the connector body 1111 contacts the second contact location 1235 on the contact member 1231 when the connector 1110 is inserted into the passage 1215. When the key 1115 engages the second contact location 1235, the key 1115 pushes against the second contact location 1235 to move the third contact location 1236 against the bias of the resilient section 1234 toward the exterior of the adapter housing 1210 sufficient to contact the contact pads and tracings on the printed circuit board 1220.
As discussed above, a processor (e.g., processor 217 of
In accordance with some aspects, the contact members 1231 of a media reading interface 1230 are configured to form a complete circuit with the printed circuit board 1220 only when a portion (e.g., the key 1115) of a fiber optic connector 1110 is inserted within the respective passage 1215. For example, the second contact locations 1235 of each contact member 1231 can be configured to raise the third contact location 1236 external of the housing 1210 through the slot 1214 when the second contact location 1235 is lifted by the key 1115.
Accordingly, the contact members 1231 can function as presence detection sensors or switches. For example, a completion of a circuit between the printed circuit board 1220 and a media reading interface 1230 can indicate that fiber optic connector 1110 is received within the passage 1215. In other example implementations, the contact members 1231 can be configured to complete the circuit until one or more portions are pushed away from a shorting rod by a media segment. In accordance with other aspects, some implementations of the contact members 1231 can be configured to form a complete circuit with the printed circuit board 1220 regardless of whether a media segment is received in the passage 1215.
If the connector 1110 inserted into the passage 1215 carries a storage device 1130;, then insertion of the connector 1110 sufficiently far into the passage 1215 aligns one or more contact pads 1132 on a storage device 1130 with contact members 1231 of the media reading interface 1230. Accordingly, the processor (e.g., a main processor) coupled to the printed circuit board 1220 is communicatively coupled to the storage device 1130 of the fiber optic connector 1110 through the contact member 1231. In some implementations, the second contact location 1235 of each contact member 1231 is aligned with one of the contact pads 1132 of a storage device 1130 when the connector 1110 is fully inserted into the passage 1215. In other implementations, the second contact locations 1235 are sufficiently aligned with the contact pads 1132 to enable communication between the printed circuit board 1220 and the storage device 1130 even before the connector 1110 is fully inserted into the passage 1215.
As shown in
One example dust cap 1250 is shown in
In the example shown, each dust cap 1250 is a duplex dust cap that includes two insertion members 1252. In other implementations, however, each dust cap 1250 can include greater or fewer insertion members 1252. In the example shown, each insertion member 1252 is shaped similarly to a fiber optic connector that is configured to be retained at a port of each passage 1215, 1215. For example, each insertion member 1252 can include a retaining member 1253 that is configured to interface with the latch engagement structures 1217, 1217 of the adapter housing 1210, 1210.
In some implementations, the dust caps 1250 are shaped and configured to avoid triggering the presence detection sensor/switch formed by the media reading interfaces (e.g., see
In other implementations, the dust caps 1250 may include storage devices containing physical layer information. In such implementations, the dust caps 1250 may be shaped and configured to trigger the presence switch through interaction with the contact members 1231, 1231 and to be read through the media reading interfaces 1230, 1230 of the passage 1215, 1215.
One or more example connector arrangements 2100 (
In the example shown in
In the example shown, each coupler housing 2210 defines a single passage 2215 extending between opposite open ends. In other example implementations, however, each coupler housing 2210 can include a greater number (e.g., two, three, four, six, eight, twelve, etc.) of passages 2215. Each open end of each passage 2215 is configured to receive a segment of communications media (e.g., a connectorized end of an optical fiber) 1010. In other implementations, the example connector system 2000 can include greater or fewer coupler housings 2210.
For ease in understanding, only portions of the example printed circuit boards 2220 of the connector system 2000 are shown in
One example coupler housing 2210 is shown in
The example coupler housing 2210 is formed from opposing sides 2211 interconnected by first and second ends 2212. The sides 2211 and ends 2212 each extend between an open front and an open rear to define passages 2215. In the example shown in
In some implementations, flexible latching tabs 2219 are located at the entrances of the passages 2215 to aid in retaining connector arrangements within the passages 2215. In the example shown, each latching tab 2219 defines a ramped surface and latching surface. The coupler housings 2210 also define channels 2218 extending partly along the length of the passages 2215 (e.g., see
Each adapter housing 2210 includes at least one media reading interface 2230 (e.g., see
The connector arrangement 2100 is configured to store physical layer information (e.g., media information). For example, the physical layer information can be stored in a memory device 2130 mounted on or in the connector body 2110. In the example shown in
One example storage device 2130 includes a printed circuit board 2131 to which memory circuitry can be arranged. In one example embodiment, the storage device 2130 includes an EEPROM circuit arranged on the printed circuit board 2131. In other embodiments, however, the storage device 2130 can include any suitable type of memory. In the example shown in
In the example shown in
In the example shown, the second media reading interface 2230B is flipped (i.e., located on an opposite side of the housing 2210) relative to the first media reading interface 2230A (e.g., see
In the example shown in
In other implementations, each major surface 2212 of the adapter 2210 may accommodate the media reading interfaces 2130 for some of the front ports and some of the rear ports. For example, in one implementation, each major surface 2212 accommodates the media reading interfaces for alternating ones of the front and rear ports. In particular, a first slot in the first major surface 2212 may accommodate a media reading interface 2130 for a front port of a first passage 2215 and a first slot 2214 in the second major surface 2212 may accommodate a media reading interface 2130 for a rear port of the first passage 2215. A second slot 2214 in the first major surface 2212 may accommodate a media reading interface 2130 for a rear port of a second passage 2215 and a second slot 2214 in the second major surface 2212 may accommodate a media reading interface 2130 for a front port of the second passage 2215. Such configurations also enable each slot 2214 to extend more than half-way between the front and rear of the adapter 2210.
Lengthening the slots 2214 enables longer contact members 2231 to be received within each slot 2214. For example, each contact member 2231 may extend at least half-way across the adapter 2210 between the front and rear of the adapter 2210. In certain implementations, each contact member 2231 may extend across a majority of the distance between the front and rear of the adapter 2210. Lengthening the contact members 2231 increases the beam length of each contact member 2231. The beam length affects the ability of the contact member 2231 to deflect toward and away from the circuit boards 2220.
In general, each media reading interface 2230 is formed from one or more contact members 2231. Portions of the contact members 2231 extend into the passage 2215 of the MPO adapter 2210 through the respective channel 2218 (e.g., see
In some implementations, the contact members 2231 of a single media reading interface 2230 are positioned in a staggered configuration to facilitate access to the contact pads 2132 on the connector storage device 2130 of a connector arrangement 2100. For example, as shown in
One example type of contact member 2231 is shown in
In the example shown in
The example contact member 2231 shown includes a base 2232 that is configured to be positioned within a slot 2214 defined by an adapter 2210. The base 2232 of certain types of contact members 2231 is configured to secure (e.g., snap-fit, latch, pressure-fit, etc.) to the adapter 1210. First and second legs 2241, 2242 extend from the base 2232. A first arm 2234 extends from the first leg 2241 and defines a first moveable contact location 2235 between the two legs 2241, 2242 (e.g., at a distal end of the arm 2234).
At least the first moveable contact location 2235 is aligned and configured to extend outwardly of the adapter housing 2210 through the slots 2214 to touch a first contact pad on the corresponding circuit board 2220 (e.g., see
A second arm 2236 extends from the second leg 2242 to define a resilient section 2237, a second moveable contact location 2238, and a third moveable contact location 2239. In one implementation, the second contact location 2238 defines a trough located on the second leg 2234 between the resilient section 2237 and the third contact location 2239. The resilient section 2237 is configured to bias the second contact location 2238 towards the channel 2218 (e.g., see
The third contact location 2239 is configured to be positioned initially within the slot 2214. The resilient section 2237 is configured to bias the third contact location 2239 through the slot 2214 to an exterior of the housing 2210 when a connector arrangement 2100 or other media segment pushes against the second contact location 2238. For example, inserting an MPO connector 2110 into a connection end of a passage 2215 of an MPO adapter 2210 would cause the storage section 2115 of the connector housing 2110 to slide through the channel 2218 and to engage the second contact location 2238 of each contact member 2231 associated with that connection end of the passage 2215. The storage section 2115 would push outwardly on the second contact location 2238, which would push the third contact location 2239 through the slots 2214 and toward the printed circuit board 2220 mounted to the adapter 2210 adjacent the slots 2214 (see
As discussed above, a processor (e.g., processor 217 of
In accordance with some aspects, the contact members 2231 are configured to selectively form a complete circuit with one or more of the printed circuit boards 2220. For example, each printed circuit board 2220 may include two contact pads for each contact member. In certain implementations, a first portion of each contact member 2231 touches a first of the contact pads and a second portion of each contact member 2231 selectively touches a second of the contact pads. The processor coupled to the circuit board 2220 may determine when the circuit is complete. Accordingly, the contact members 2231 can function as presence detection sensors for determining whether a media segment has been inserted into the passages 2215.
In certain implementations, the first moveable contact 2235 of each contact member is configured to contact one of the contact pads of the circuit board 2220. In one implementation, the first moveable contact location 2235 is configured to permanently touch the contact pad as long as the circuit board 2220 and contact member 2231 are assembled on the adapter 2210. The third contact location 2239 of certain types of contact members 2231 is configured to touch a second contact pad of the printed circuit board 2220 only when a segment of physical communications media (e.g., an MPO connector 2110) is inserted within an adapter passage 2215 and pushes the second contact location 2238 out of the channel 2218, which pushes the third contact location 2239 through the slot 2214 and against the circuit board 2220. In accordance with other aspects, the contact members 2231 are configured to form a complete circuit with the printed circuit board 2220 regardless of whether a media segment is received in the passage 2215.
Referring to
A retaining section 2252 extends outwardly from a second side of the cover 2251. The retaining section 2252 defines a concave contour 2256 extending between two fingers 2258. One or both fingers 2258 include lugs 2255 that are configured to interact with the flexible tabs 2219 of the adapter housing 2210 to retain the dust cap 2250 within the passage 2215. In the example shown, each lug 2255 defines a ramped surface.
In some implementations, the retaining section 2252 is configured to fit within the passage 2215 without pressing against the second contact location 2238 of each contact member 2231 of the first media reading interface 2230 (see
The communications coupler assembly 4200 is configured to be mounted to a connector assembly, such as a communications blade or a communications panel. One or more connector arrangements 4100, which terminate segments 4010 of communications media, are configured to communicatively couple to other segments of physical communications media at the coupler assembly 4200 (e.g., see
In accordance with some aspects, each connector arrangement 4100 is configured to terminate a single segment of physical communications media. For example, each connector arrangement 4100 can include a single connector 4110 that terminates a single optical fiber or a single electrical conductor (
In accordance with still other aspects, each connector arrangement 4100 can include one or more connectors, each of which terminates a plurality of physical media segments (e.g., see connector arrangement 2100, 2100, and 5100 of
In accordance with some aspects, each communications coupler assembly 4200 is configured to form a single link between segments of physical communications media 4010. For example, each communications coupler assembly 4200 can define a single passage at which a first connector arrangement is coupled to a second connector arrangement. In accordance with other aspects, however, each communications coupler assembly 4200 is configured to form two or more links between segments of physical communications media. For example, in the example shown in
In some implementations, each passage 4215 of the communications coupler assembly 4200 is configured to form a single link between first and second connector arrangements 4100. In other example implementations, two or more passages 4215 can form a single link between connector arrangements 4100 (e.g., two sets of ports can form a single link between two duplex connector arrangements). In still other example implementations, each communications coupler assembly 4200 can form a one-to-many link. For example, the communications coupler assembly 4200 can connect a duplex connector arrangement to two simplex connector arrangements.
Example implementations of connector arrangements 4100 are shown in
As shown in
One example clip 4150 is shown in
Each connector arrangement 4100 is configured to store physical layer information. For example, a storage device 4130 may be installed on or in the body 4111 of one or more of the fiber optic connectors 4110 of each connector arrangement 4100. In the example shown, the storage device 4130 is installed on only one fiber optic connector 4110 of a duplex connector arrangement 4100 (
One example storage device 4130 includes a printed circuit board 4131 (
As shown in
In the example shown, the cavity 4116 includes a well 4162 surrounded by a ledge 4164. The ledge 4164 is configured to support the storage device 4130. For example, the ledge 4164 may support the printed circuit board 4131 of an example storage device 4130. The well 4162 is sufficiently deep to accommodate an EEPROM circuit 4133 coupled to one side of the printed circuit board 4131. The ledge 4164 is recessed sufficiently within the connector body 4111 to enable electrical contacts 4132 provided on the opposite side of the printed circuit board 4131 to be generally flush with the key 4115 of the connector body 4111 (see
In certain implementations, the ledge 4164 has a ridged or otherwise contoured surface to facilitate mounting the storage device within the cavity 4116. For example, in some implementations, contoured sections 4166 of the ledge 4164 may increase the surface area over which an adhesive may be applied to secure the storage device 4130 within the cavity 4116. In the example shown, the contoured sections 4166 include rectangular-shaped protrusions and/or depressions. In other implementations, however, the ledge 4164 may have bumps, ridges, or some other texture to increase the surface area over which adhesive is applied.
The key 4115 also defines a recessed section or cavity 4116A in which a storage device 4130A can be positioned (e.g., see
The storage device 4130A shown in
In some implementations, the contacts 4132A have different lengths. In certain implementations, the contacts 4132A have different shapes. For example, in some implementation, the contacts 4132A include one or more contact members 4132A′ that have generally rounded ends at one or both ends of the contact members 4132A′. In certain implementations, the contacts 4132A also include one or more contact members 4132A″ that are generally L-shaped. In the example shown, the L-shaped contacts 4132A″ are longer than the rounded end contacts 4132A′. In other implementations, however, the contacts 4132A may have the same length or may each have different lengths.
The storage device 4130B shown in
The storage device 4130C shown in
The example adapter housing 4210 shown in
In the example shown, the body 4210 of the fiber optic adapter 4200 defines four passages 4215. In other implementations, the body 4210 can define greater or fewer passages 4215. For example, in some example implementations, the body 4210 of the fiber optic adapter 4200 can define a single passage 4215 that is configured to optically couple together two fiber optic connectors 4110. In other example implementations, the fiber optic adapter 4200 can define two, eight, or twelve passages 4215 that are each configured to optically couple together two fiber optic connectors 4110. In certain implementations, the adapter housing 4210 also defines latch engagement channel 4217 (
The fiber optic adapter 4210 includes one or more media reading interfaces 4230, each configured to acquire the physical layer information from the storage device 4130 of a fiber optic connector 4110 plugged into the fiber optic adapter 4210. For example, in one implementation, the adapter 4210 can include a media reading interface 4230 associated with each passage 4215. In another implementation, the adapter 4210 can include a media reading interface 4230 associated with each connection end of each passage 4215. In still other implementations, the adapter 4210 can include a media reading interface 4230 associated with each of a set of passages 4215 that accommodate a connector arrangement 4100.
For example, the quadruplex adapter 4210 shown in
In general, each media reading interface 4230 is formed from one or more contact members 4231 (see
At least a portion of each slot 4214 extends through the top surface to the passage 4215. In some implementations, the material height of the top surface is at least 0.76 mm (0.03 inches). Indeed, in some implementations, the material height of the top surface is at least 1.02 mm (0.04 inches). In certain implementations, the material height of the top surface is at least 1.27 mm (0.05 inches).
In some implementations, the media reading interface 4230 includes multiple contact members 4231. For example, in certain implementations, the media reading interface 4230 includes at least a first contact member 4231 that transfers power, at least a second contact member 4231 that transfers data, and at least a third contact member 4231 that provides grounding. In one implementation, the media reading interface 4230 includes a fourth contact member. In other implementations, the media reading interface 4230 include greater or fewer contact members 4231.
In some implementations, each contact member 4231 is retained within a separate slot 4214. For example, in the implementation shown in
In some implementations, the adapter housing 4210 has more sets 4213 of slots 4214 than media reading interfaces 4230. For example, in some implementations, each adapter housing 4210 defines a set 4213 of slots 4214 at each connection end of each passage 4215. In other implementations, however, the adapter housing 4210 may have the same number of slot sets 4213 and media reading interfaces 4231. For example, in certain implementations, each adapter housing 4210 may defines a set 4213 of slots 4214 at only one connection end of each passage 4215. In other implementations, the adapter housing 4210 may define a set 4213 of slots 4214 at each connection end of alternate passages 4215.
In some implementations, the contact members 4231 of a single media reading interface 4230 are positioned in a staggered configuration. In some implementations, the slots 4214 accommodating the staggered contact members 4231 also are staggered. For example, as shown in
In the example shown in
In some implementations, a single support wall 4205 extends along a center of the adapter housing 4210 transverse to the insertion axis AI (
As shown in
In certain implementations, the width W7 of the intermediate walls 4216 is smaller than the width W6 of the slots 4214. In some implementations, the width W6 of each slot 4214 is within the range of about 0.25 mm (0.010 inches) to about 0.64 mm (0.025 inches). Indeed, in some implementations, the width W6 of each slot 4214 is within the range of about 0.28 mm (0.011 inches) to about 0.48 mm (0.019 inches). In one implementation, the width W6 of each slot is about 0.3 mm (0.012 inches). In one implementation, the width W6 of each slot is about 0.28 mm (0.011 inches). In one implementation, the width W6 of each slot is about 0.33 mm (0.013 inches). In some implementations, the width W7 of each intermediate wall 4216 is within the range of about 0.13 mm (0.005) inches to about 0.36 mm (0.014 inches). In one implementation, the width W7 of each intermediate wall 4216 is about 0.28 mm (0.011 inches). In another implementation, the width W7 of each intermediate wall 4216 is about 0.15 mm (0.006 inches).
As shown in
The contact members 4231 extend between the slotted surface of the adapter housing 4210 and the passages 4215. Portions of each contact member 4231 engage contacts and tracings on the printed circuit board 4220 mounted to the slotted surface of the adapter housing 4210. Other portions of the contact members 4231 engage the electrical contacts 4132 of the storage members 4130 attached to any connector arrangements 4100 positioned in the passages 4215 (see
In some implementations, each media reading interface 4230 of the fiber optic adapter 4200 includes four contact members 4231 (see
In accordance with some aspects, the media reading interfaces 4230 of the adapter are configured to detect when a connector arrangement is inserted into one or more passages 4215. The contact members 4231 can function as presence detection sensors or trigger switches. In some implementations, the contact members 4231 of a media reading interface 4230 are configured to form a complete circuit with the circuit board 4220 only when a connector 4110 is inserted within a respective passage 4215. For example, at least a portion of each contact member 4231 may be configured to contact the circuit board 4220 only after being pushed toward the circuit board 4220 by a connector 4210. In other example implementations, portions of the contact members 4231 can be configured to complete a circuit until pushed away from the circuit board 4220 or a shorting rod by a connector 4110. In accordance with other aspects, however, some implementations of the contact members 4231 may be configured to form a complete circuit with the circuit board 4220 regardless of whether a connector 4110 is received in a passage 4215.
One example type of contact member 4231 is shown in
The first moveable contact section 4233 is configured to extend through the slot 4214 and engage the circuit board 4220. The first stationary contact 4237 also is configured to extend through the slot 4214 to engage the circuit board 4220. The ability of the first contact section 4233 to flex relative to the stationary contact 4237 provides tolerance for placement of the contact member 4231 relative to the circuit board 4220. The second moveable contact section 4235 is configured to extend into the passage 4215 and engage the connector 4110 positioned in the passage 4215. If a storage device 4130 is installed on the connector 4110, then the second contact surface 4235 is configured to engage the contact pads 4132 of the storage device 4130.
The third moveable contact surface 4236 is configured to selectively extend through the slot 4214 and engage the circuit board 4220. For example, the third contact surface 4236 may be configured to engage the circuit board 4220 when a connector 4110 is inserted into a passage 4215 corresponding with the contact member 4231. The example contact member 4231 also includes a resilient section 4234 that biases the third contact surface 4236 upwardly through the slot 4214 (e.g., toward the circuit board 4220). In some implementations, the resilient section 4234 defines at least a partial arc. For example, in the implementation shown in
The example contact member 4231 is configured to seat in one of the slots 4214 of the adapter housing 4210. For example, the contact member 4231 includes a base 4232 that is configured to abut the support wall 4205 of the adapter housing 4210 (see
Another end of the base 4232 defines an attachment section 4238 that engages a portion of the support wall 4205 to secure the contact member 4231 within the slot 4214. In some implementations, the attachment section 4238 of the contact member 4231 includes a first leg 4241 and a second leg 4243 extending from the base 4232 (
The example contact member 4231 also includes a third leg 4244 that extends outwardly from the base 4232 generally parallel with the second leg 4243. A distal end of the third leg 4244 bends or curves upwardly toward the circuit board 4220. In the example shown, the third leg 4244 is generally J-shaped. In other implementations, the third leg 4244 may be L-shaped, C-shaped, V-shaped, etc. The first contact surface 4233 is defined at the distal end of the third leg 4244. In the example shown, the distal end of the third leg 4244 defines an arched or ball-shaped first contact surface 4233. In one implementation, the first contact section 4233 and/or the stationary contact 4237 may provide grounding for the contact member 4231 through the circuit board 4220.
The contact member 4231 also includes a fourth leg 4245 that extends outwardly from the base 4232. In the example shown, the fourth leg 4245 extends outwardly between the second and third legs 4243, 4244 and generally parallel to the second and third legs 4243, 4244. The fourth leg 4245 separates into first arm 4246, which defines the third contact surface 4236, and a second arm 4247, which defines the second contact surface 4235. The first arm 4246 extends upwardly from the fourth leg 4245 towards the circuit board 4220. For example, in some implementations, the first arm 4246 arcs upwardly into a planar extension that terminates at the third contact surface 4236. In the example shown, the third contact surface 4236 defines an arched or ball-shaped distal end of the first arm 4246.
The second arm 4247 initially extends away from the fourth leg 4245 and subsequently extends back towards the base 4232 to increase the beam length of the contact 4231. For example, in some implementations, the second arm 4247 extends downwardly to define the resilient section 4234 and upwardly into a bend section 4239. From the bend section 4239, the second arm 4247 changes direction (i.e., curves, bends, folds, arcs, angles, etc.) downwardly and back toward the base 4232 along an elongated section 4248, which may be straight or contoured. In the example shown, the elongated section 4248 defines a bend about part-way through.
A tail 4249 extends from the elongated section 4248 toward the base 4230. In the example shown, the tail 4249 curves downwardly to define the second contact surface 4235 before curving upwardly towards the base 4232. As shown in
At least the tail 4249 of the contact member 4231 is configured to deflect or flex when the front surface 4118 of the key 4115 of a connector 4110 pushes against a portion of the second arm 4247 of the contact member 4231 when a connector 4110 is inserted into the socket 4215. In the example shown, the tail 4249 and the elongated portion 4248 flex when deflected by the key 4115. For example, the elongated portion 4248 and tail 4249 flex when the deflecting surface 4118 pushes against an outer surface of the elongated section 4248. In some implementations, the tail 4249 defines the second contact surface 4235. In other implementations, an outer surface of the elongated section 4248 defines the second contact surface 4235. In still other implementations, the elongated section 4248 and the tail 4249 cooperate to define the second contact section 4235.
The resilient section 4234 is configured to transfer the force applied to a second arm 4247 of the contact member 4231 to the first arm 4246. For example, in some implementations, the resilient section 4234 is configured to lift the first arm 4246 to swipe the third contact surface 4236 against the printed circuit board 4220 (see
In some implementations, the body of the contact member 4231 extends between a first and second end. In the example shown in
The contact member 4231 defines a body having a circumferential edge 4240 (
Portions of the planar surfaces of the contact member 4231 may increase and/or decrease in width. For example, in the example shown in
In one implementation, the contact member 4231 is formed monolithically (e.g., from a continuous sheet of metal or other material). For example, in some implementations, the contact member 4231 may be manufactured by cutting a planar sheet of metal or other material. In other implementations, the contact member 4231 may be manufactured by etching a planar sheet of metal or other material. In other implementations, the contact member 4231 may be manufactured by laser trimming a planar sheet of metal or other material. In still other implementations, the contact member 4231 may be manufactured by stamping a planar sheet of metal or other material.
In some implementations, a support portion 4209 (
The tail 4249 of the contact member 4231 extends into the passage 4215 associated with the slot 4214. Inserting the connector 4110 into the passage 4215 causes the deflection surface 4118 of the key 4115 of a connector 4110 to press against the outer surface of the elongated section 4248 (see
In some implementations, the connector 4110 does not include a storage device 4130. For example, the connector 4110 may be part of a duplex connector arrangement 4100 in which the other connector 4110 holds the storage device 4130. In other implementations, the connector 4110 may be an existing connector that does not store physical layer information. In other implementations, however, the connector 4110 may include a storage device 4130. In such implementations, the second contact surface 4235 of the contact member 4231 slides or wipes across the surface of the contacts 4132 of the storage device 4130 during insertion of the connector (see
In some implementations, the storage device 4130 is stored in a cavity defined only in a top of the key 4115 (e.g., see
In other implementations, the storage device 4130 is accessible through a recess in the deflection surface 4118 (e.g., see
As discussed above, a processor (e.g., processor 217 of
Removing the connector 4110 from the passage 4215 releases the second arm 4247 from the upwardly biased position (see
The example circuit board 4220 includes a plurality of first contact pads 4223 and a plurality of second contact pads 4224 spaced from the first contact pads 4223. In certain implementations, the first contact pads 4223 are laterally aligned with each other and the second contact pads 4224 are laterally aligned with each other. In other implementations, however, the first contact pads 4223 may be laterally offset or staggered from each other and/or the second contact pads 4224 may be laterally offset of staggered from each other. In certain implementations, each of the first contact pads 4223 is longitudinally aligned with one of the second contact pads 4224 to form a landing pair. In other implementations, however, the first and second contact pads 4223, 4224 may be longitudinally offset from each other.
A media reading interface (e.g., media reading interface 4230) may be seated on the printed circuit board 4220. In the example shown, the first moveable contact surface 4233 of each contact member 4231 of the media reading interface 4230 touches one of the first contact pads 4223. In certain implementations, the stationary contacts 4237-also touch the first contact pads 4223. The third moveable contact surface 4239 of each contact member 4231 is configured to selectively touch the second contact pad 4224 that forms a landing pair with the first contact pad 4223.
The coupler assembly 5200 includes one or more coupler housings 5210. At least one coupler housing 5210 is sandwiched between a first circuit board 5220A and a second circuit board 5220B (e.g., via fasteners 5222A, 5222B). In some implementations, multiple (e.g., two, three, four, eight, twelve, sixteen, twenty, etc.) coupler housings 5210 may be sandwiched between two circuit boards (e.g., see
For ease in understanding, only portions of the example printed circuit boards 5220A, 5220B of the connector system 5000 are shown in
One example coupler housing 5210 is shown in
In the example shown, each coupler housing 5210 is implemented as a fiber optic adapter configured to receive Multi-fiber Push-On (MPO) connectors. Each passage 5215 of the MPO adapters 5210 is configured to align and connect two MPO connector arrangements 5100 (see
In the example shown in
The adapter 5210 also includes mounting stations 5217 at which fasteners 5222 (
In some implementations, the adapter 5210 also includes alignment lugs 5216 that facilitate mounting the adapter 5210 to the circuit boards 5220 in the correct orientation. For example, the alignment lugs 5216 may align with openings 5226 (
The MPO adapter 5210 also defines channels 5218 extending partly along the length of the passages 5215 (e.g., see
Each adapter housing 5210 includes at least one media reading interface 5230 (e.g., see
In certain implementations, the connector 5110 includes a pin arrangement 5119 that extends from a front of the ferrule 5112. In other implementations, the connector 5110 defines openings in the ferrule 5112 for receiving the pin arrangement 5119 of another connector 5100 to align the ferrules 5112 of the two connectors 5110 (e.g., see
Each connector arrangement 5100 is configured to store physical layer information (e.g., media information). For example, the physical layer information can be stored in a memory device 5130 mounted on or in the connector 5110. One example storage device 5130 includes a printed circuit board 5131 on which memory circuitry can be arranged (e.g., see
As shown in
In the example shown, the cavity 5116 includes a well 5162 surrounded by a ledge 5164 (see
In certain implementations, the ledge 5164 has a ridged or otherwise contoured surface to facilitate mounting the storage device within the cavity 5116. For example, in some implementations, contoured sections 5166 of the ledge 5164 may increase the surface area over which an adhesive may be applied to secure the storage device 5130 within the cavity 5116. In the example shown, the contoured sections 5166 include rectangular-shaped protrusions and/or depressions. In other implementations, however, the ledge 5164 may have bumps, ridges, or some other texture to increase the surface area over which adhesive is applied.
The storage device 5130A shown in
In some implementations, the contacts 5132A have different lengths. In certain implementations, the contacts 5132A have different shapes. For example, in some implementation, the contacts 5132A include one or more contact members 5132A′ that have generally rounded ends opposite the deflecting end 5118 of the connector housing 5110. In certain implementations, the contacts 5132A also include one or more contact members 5132A″ that are generally L-shaped. In the example shown, the L-shaped contacts 5132A″ are longer than the rounded end contacts 5132A′. In other implementations, however, the contacts 5132A may have the same length or may each have different lengths.
The storage device 5130B shown in
The storage device 5130C shown in
In general, memory circuitry is arranged on a circuit board 5131 of the storage device 5130 and connected to the contacts 5132 via conductive tracings. In one example embodiment, the storage device 5130 includes an EEPROM circuit arranged on the printed circuit board 5131. In other embodiments, however, the storage device 5130 can include any suitable type of memory. In some implementations, the cavity 5116 is two-tiered, thereby providing a shoulder on which the storage device 5130 can rest and space to accommodate circuitry (e.g., memory 5133) located on a bottom of the storage device 5130. In other implementations, the storage device 5130 can be otherwise mounted to the connector housing 5110.
In some implementations, the MPO adapter housing 5210 includes a first media reading interface 5230A and a second media reading interface 5230B. For example, in some implementations, the first media reading interface 5230A is associated with a first connection end of the passage 5215 and the second media reading interface 5230B is associated with a second connection end of the passage 5215. In the example shown, the second media reading interface 5230B is flipped (i.e., located on an opposite side of the housing 5210) relative to the first media reading interface 5230A. In some such implementations, the channel 5218 extending inwardly from the first connection end of the passage 5215 also is flipped with respect to the channel 5218 extending inwardly from the second end of the passage 5215 (compare
In the example shown in
In other implementations, each major surface 5212 of the adapter 5210 may accommodate the media reading interfaces 5130 for some of the front ports and some of the rear ports. For example, in one implementation, each major surface 5212 accommodates the media reading interfaces for alternating ones of the front and rear ports. In particular, a first slot in the first major surface 5212 may accommodate a media reading interface 5130 for a front port of a first passage 5215 and a first slot 5214 in the second major surface 5212 may accommodate a media reading interface 5130 for a rear port of the first passage 5215. A second slot 5214 in the first major surface 5212 may accommodate a media reading interface 5130 for a rear port of a second passage 5215 and a second slot 5214 in the second major surface 5212 may accommodate a media reading interface 5130 for a front port of the second passage 5215. Such configurations also enable each slot 5214 to extend more than half-way between the front and rear of the adapter 5210.
Lengthening the slots 5214 enables longer contact members 5231 to be received within each slot 5214. For example, each contact member 5231 may extend at least half-way across the adapter 5210 between the front and rear of the adapter 5210. In certain implementations, each contact member 5231 may extend across a majority of the distance between the front and rear of the adapter 5210. Lengthening the contact members 5231 increases the beam length of each contact member 5231. The beam length affects the ability of the contact member 5231 to deflect toward and away from the circuit boards 5220.
In some implementations, the contact members 5231 of a single media reading interface 5230 are positioned in a staggered configuration to facilitate access to the contacts 5132 on the connector storage device 5130 of a connector arrangement 5100. For example, alternating contact members 5231 can be staggered between at least front and rear locations within the channels 5218.
In some implementations, each media reading interface 5230 includes about four contact members 5231 (see
One example type of contact member 5231 suitable for use in forming a media reading interface 5230 is shown in
The example contact member 5231 shown includes a base 5232 that is configured to be positioned within a slot 5214 defined by an adapter 5210. The base 5232 of certain types of contact members 5231 is configured to secure (e.g., snap-fit, latch, pressure-fit, etc.) to the adapter 5210. A first arm 5234 of the contact member 5231 defines the first moveable contact location 5235 (e.g., at a distal end of the first arm 5234). A second arm 5236 of the contact member 5231 defines a resilient section 5237, the second moveable contact location 5238, and the third moveable contact location 5239. The base 5232 of the contact member body 5240 defines a support surface 5241 extending between first and second legs 5242, 5243, respectively. The first arm 5234 extends from the first leg 5242 and the second arm 5236 extends from the second leg 5243. In the example shown, the first and second arms 5234, 5236 extend in generally the same direction from the first and second legs 5242, 5243.
Mounting sections 5244 are provided on the base 5232 between the support surface 5241 and the legs 5242, 5243. In the example shown, the mounting sections 5244 each include a recessed notch and a protruding bump to facilitate securing the base 5232 in a slot 5214 of the adapter 5210. In other implementations, however, other types of mounting configurations may be utilized. The second leg 5243 and the second arm 5236 define a second support surface 5245. In the example shown, the second support surface 5245 is rounded. In other implementations, the second support surface 5245 may define a right angle or an oblique angle.
At least the first moveable contact location 5235 is aligned and configured to extend outwardly of the adapter housing 5210 through the slots 5214 to touch a first contact pad on the corresponding circuit board 5220 (e.g., see
In some implementations, the resilient section 5237 is implemented as a looped/bent section of the second arm 5236. In one implementation, the resilient section 5237 of the second arm 5236 is formed from one or more elongated sections connected by U-shaped bends. In other implementations, the second arm 5236 can otherwise include springs, reduced width sections, or portions formed from more resilient materials. In the example shown, the resilient section 5237 is formed from a first elongated section 5246 extending away from the second leg 5243, a second elongated section 5247 extending generally parallel to the first elongated section 5246 back towards the second leg 5243, and a third elongated section 5248 extending generally parallel to the first and second elongated sections 5246, 5247 and away from the second leg 5243.
The third elongated section 5248 includes a trough that defines the second contact location 5238. In certain implementations, the trough defining the second contact location 5238 is located at an intermediate portion of the third elongated section 5248. In one implementation, the trough defining the second contact location 5238 is located at about the center of the third elongated member 5248. A tail 5249 extends from the third elongated section 5248 to define the third contact location 5239. In some implementations, the tail 5249 is generally S-shaped. In other implementations, however, the tail 5249 may be C-shaped, J-shaped, U-shaped, L-shaped, or linear.
In some implementations, the body of the contact member 5231 extends between a first and second end. In the example shown in
The contact member 5231 defines a body having a circumferential edge 5240 (
Portions of the planar surfaces of the contact member 5231 may increase and/or decrease in width. For example, in the example shown in
In some implementations, the contact member 5231 is formed monolithically (e.g., from a continuous sheet of metal or other material). For example, in some implementations, the contact member 5231 may be manufactured by cutting a planar sheet of metal or other material. In other implementations, the contact member 5231 may be manufactured by etching a planar sheet of metal or other material. In other implementations, the contact member 5231 may be manufactured by laser trimming a planar sheet of metal or other material. In still other implementations, the contact member 5231 may be manufactured by stamping a planar sheet of metal or other material.
The adapter housing 5210 defines at least a first slot 5214F extending through a top end 5212F of the adapter 5210 and at least a second slot 5214S extending through a bottom end 5212S of the adapter 5210. In some implementations, each end 5212F, 5212S of the adapter housing 5210 defines one slot 5214 that is configured to hold one or more contact members 5231. In other implementations, each end 5212F, 5212S of the adapter housing 5210 defines multiple slots 5214F, 5214S, which are each configured to hold one or more contact members 5231. The slots 5214F, 5214S extend at least part-way across the passage 5215. In the example shown, each slot 5214F, 5214S extends across a majority of the length of the passage 5215. In other implementations, each slot 5214F, 5214S may extend a greater or lesser distance across the passage 5215.
As discussed above, each adapter 5210 includes a first channel 5218F extending inwardly from a front connection end of the passage 5215 and a second channel 5218S extending inwardly from a rear connection end of the passage 5215. Each channel 5218F, 5218S is configured to accommodate the key 5215 of the respective connector 5100F, 5100S. In some implementations, each channel 5218F, 5218S extends about half-way through the passage 5215. In other implementations, each channel 5218F, 5218S extends a greater or lesser distance through the passage 5215. Each channel 5218F, 5218S is associated with one of the slots 5214F, 5214S. In some implementations, each channel 5218F, 5218S extends fully across the respective slot 5214F, 5214S. In other implementations, each channel 5218F, 5218S extends only partially across the respective slot 5214F, 5214S.
In some implementations, at least a portion of each slot 5214F, 5214S extends partially through the top and bottom ends 5212F, 5212S of the adapter 5210. For example, one or more portions of the slots 5214F, 5214S can extend through the respective ends 5212F, 5212S to recessed surfaces 5205 (
A first media reading interface 5230F is positioned in the first slot 5214F and a second media reading interface 5230S is positioned in the second slot 5214B. In some implementations, each media reading interface 5230F, 5230S includes one or more contact members 5231 (see
In the example shown, the contact members 5231 are staggered within the slots 5214F, 5214S. In other implementations, the contact members 5231 may be laterally aligned within the slots 5214F, 5214S. In some implementations, the first and second ends 5212F, 5212S of the adapter 5210 define intermediate walls that extend between pairs of adjacent contact members 5231. The intermediate walls inhibit contact between adjacent contact members 5231. In certain implementations, the intermediate walls extend fully between the adjacent contact members 5231. In other implementations, intermediate wall sections 5204 extend between portions of the adjacent contact members 5231.
In the example shown in
In some implementations, an intermediate wall section 5204 in each slot 5214F, 5214S extends across the first contact location 5235 of one or both contact members 5231 in each pair of adjacent contact members 5231 (e.g., see intermediate wall section 5204 in slot 5214F in
In some implementations, an intermediate wall section 5204 extends across at least a portion of the second arm 5236 of one or both contact members 5231 in each pair of adjacent contact members 5231. In certain implementations, the intermediate wall section 5204 extends between the U-shaped bends joining the second and third elongated sections 5247, 5248 of the resilient sections 5237 of one or more contact members 5231 in the slot 5214F, 5214S. In certain implementations, the intermediate wall section 5204 extends across the second leg 5243 of one or both contact members 5231 in each pair of adjacent contact members 5231. In certain implementations, the support walls 5206 extend laterally between the intermediate walls 5204 (e.g., see
In some implementations, an intermediate wall section 5204 extends across the third contact location 5239 of one or both contact members 5231 in each pair of adjacent contact members 5231. For example, the intermediate wall section 5204 may inhibit lateral bending of the tail 5239 of one or more contact members 5231 within the slot 5214F, 5214S. In certain implementations, the intermediate wall section 5204 extends between the U-shaped bends joining the first and second elongated sections 5246, 5247 of the resilient sections 5237 of one or more contact members 5231 in the slot 5214F, 5214S.
As discussed above, a processor (e.g., processor 217 of
In accordance with some aspects, the contact members 5231 are configured to selectively form a complete circuit with one or more of the printed circuit boards 5220. For example, each printed circuit board 5220 may include two contact pads for each contact member. In certain implementations, a first portion of each contact member 5231 touches a first of the contact pads and a second portion of each contact member 5231 selectively touches a second of the contact pads. The processor coupled to the circuit board 5220 may determine when the circuit is complete. Accordingly, the contact members 5231 can function as presence detection sensors for determining whether a media segment has been inserted into the passages 5215.
In certain implementations, the first moveable contact 5235 of each contact member is configured to contact one of the contact pads of the circuit board 5220. In one implementation, the first moveable contact location 5235 is configured to permanently touch the contact pad as long as the circuit board 5220 and contact member 5231 are assembled on the adapter 5210. The third contact location 5239 of certain types of contact members 5231 is configured to touch a second contact pad of the printed circuit board 5220 only when a segment of physical communications media (e.g., an MPO connector 5110) is inserted within an adapter passage 5215 and pushes the second contact location 5238 out of the channel 2218, which pushes the third contact location 5239 through the slot 5214 and against the circuit board 5220. In accordance with other aspects, the contact members 5231 are configured to form a complete circuit with the printed circuit board 5220 regardless of whether a media segment is received in the passage 5215.
For example, as shown in
The resilient section 5237 (
When a connector arrangement (e.g., see first connector arrangement 5100F of
The third contact location 5239 of each contact member 5231 is configured to be positioned initially within the shoulder section 5209 of the respective slot 5214F, 5214S of the adapter housing 5210. In some implementations, the distal end of the tail 5249 rests against the shoulder 5209 when a respective connector arrangement 5100F, 5100S is not within the passage 5215. In other implementations, the distal end of the tail 5249 is located between the shoulder 5209 and the respective printed circuit board 5220 when the respective connector arrangement 5100F, 5100S is not within the passage 5215.
The resilient section 5237 of each contact member 5231 is configured to bias the third contact location 5239 away from the shoulder 5209 and towards the respective circuit board 5220F, 5220S when the respective connector arrangement 5100F, 5100S or other media segment pushes against the second contact location 5238 (see
In accordance with some aspects, the contact members 5231 are configured to form a complete circuit with one or more of the printed circuit boards 5220F, 5220S only when a segment of physical communications media is inserted within the adapter passage 5215. For example, the third contact location 5239 of each contact member 5231 can be configured to contact the respective circuit board 5220F, 5220S only after being pushed through the respective slot 5214F, 5214S by the media segment. Accordingly, certain types of contact members 5231 function as presence detection sensors for determining whether a media segment has been inserted into the passages 5215.
In certain implementations, the resilient section 5237 of each contact member 5231 is configured to bias the third contact surface 5239 towards the circuit board 5220F, 5220S when the key of a connectorized media segment (e.g., MPO connectors 5100F, 5100S) is inserted into the passage 5215 regardless of whether a storage device 5130 is provided on or in the key 5115. In accordance with other aspects, the contact members 5231 are configured to form a complete circuit with the respective circuit board 5220F, 5220S regardless of whether a media segment is received in the passage 5215.
A media reading interface (e.g., media reading interface 5230) may be seated on the printed circuit board 5220. In the example shown, the first moveable contact surface 5235 of each contact member 5231 of the media reading interface 5230 touches one of the first contact pads 5223. In certain implementations, the stationary contacts 5223 also touch the first contact pads 5223. The third moveable contact surface 5239 of each contact member 5231 is configured to selectively touch the second contact pad 5224 that forms a landing pair with the first contact pad 5223. In certain implementations, at least a portion of the resilient section 5237 also selectively touches the second contact pad 5224 (see
Referring to
In some implementations, the retaining section 5252 is configured to fit within the passage 5215 without pressing against the second contact location 5238 of each contact member 5231 of the media reading interfaces 5230 (see
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many implementations can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
This application is a continuation of U.S. application Ser. No. 13/025,784, filed Feb. 11, 2011, now U.S. Pat. No. 9,140,859, which application claims the benefit of U.S. Provisional Application No. 61/303,961, filed Feb. 12, 2010, titled “Fiber Plugs and Adapters for Managed Connectivity;” U.S. Provisional Application No. 61/413,828, filed Nov. 15, 2010, titled “Fiber Plugs and Adapters for Managed Connectivity;” and U.S. Provisional Application No. 61/437,504, filed Jan. 28, 2011, titled “Fiber Plugs and Adapters for Managed Connectivity,” which applications are incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
3243761 | Piorunneck | Mar 1966 | A |
RE26692 | Ruehlemann | Oct 1969 | E |
3954320 | Hardesty | May 1976 | A |
4127317 | Tyree | Nov 1978 | A |
4737120 | Grabbe et al. | Apr 1988 | A |
4953194 | Hansen et al. | Aug 1990 | A |
4968929 | Hauck et al. | Nov 1990 | A |
5041005 | McHugh | Aug 1991 | A |
5052940 | Bengal | Oct 1991 | A |
5064381 | Lin | Nov 1991 | A |
5107532 | Hansen et al. | Apr 1992 | A |
5161988 | Krupka | Nov 1992 | A |
5166970 | Ward | Nov 1992 | A |
5199895 | Chang | Apr 1993 | 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 |
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 |
5579425 | Lampert et al. | Nov 1996 | A |
5674085 | Davis et al. | Oct 1997 | A |
5685741 | Dewey et al. | Nov 1997 | A |
5712942 | Jennings et al. | Jan 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 |
5980323 | Bricaud et al. | Nov 1999 | A |
6002331 | Laor | Dec 1999 | 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 |
6364694 | Lien | Apr 2002 | B1 |
6375362 | Heiles et al. | Apr 2002 | B1 |
6409392 | Lampert et al. | Jun 2002 | B1 |
6421322 | Koziy et al. | Jul 2002 | B1 |
6422895 | Lien | Jul 2002 | B1 |
6424710 | Bartolutti et al. | Jul 2002 | B1 |
6437894 | Gilbert et al. | Aug 2002 | B1 |
6456768 | Boncek et al. | 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 |
6652155 | Lampert | Nov 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 |
6850685 | Tinucci et al. | Feb 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 |
6971895 | Sago et al. | Dec 2005 | B2 |
6976867 | Navarro et al. | Dec 2005 | B2 |
7077710 | Haggay et al. | Jul 2006 | B2 |
7080945 | Colombo et al. | Jul 2006 | B2 |
7081808 | Colombo et al. | Jul 2006 | B2 |
7088880 | Gershman | Aug 2006 | B1 |
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 | Jun 2007 | B1 |
7234944 | Nordin et al. | Jun 2007 | B2 |
7241157 | Zhuang et al. | Jul 2007 | B2 |
7297018 | Caveney et al. | Nov 2007 | B2 |
7300214 | Doo et al. | Nov 2007 | B2 |
7312715 | Shalts et al. | Dec 2007 | B2 |
D559186 | Kelmer | Jan 2008 | S |
7315224 | Gurovich et al. | Jan 2008 | B2 |
7352289 | Harris | Apr 2008 | B1 |
7356208 | Becker | Apr 2008 | B2 |
7370106 | Caveney | May 2008 | B2 |
7384300 | Salgado et al. | Jun 2008 | B1 |
7396245 | Huang et al. | Jul 2008 | B2 |
7458517 | Durrant et al. | Dec 2008 | B2 |
7479032 | Hoath et al. | Jan 2009 | B2 |
7490996 | Sommer | Feb 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 |
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 | Gatnau Navarro et al. | Sep 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 |
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 |
8172468 | Jones et al. | May 2012 | B2 |
8282425 | Bopp et al. | Oct 2012 | B2 |
8287316 | Pepe et al. | Oct 2012 | B2 |
8477031 | McNally et al. | Jul 2013 | B2 |
8596882 | Smrha et al. | Dec 2013 | B2 |
8690593 | Anderson et al. | Apr 2014 | B2 |
8696369 | Mattson et al. | Apr 2014 | B2 |
8715012 | Taylor | May 2014 | B2 |
8757895 | Petersen | Jun 2014 | B2 |
8923013 | Anderson et al. | Dec 2014 | B2 |
8934252 | Anderson et al. | Jan 2015 | B2 |
8934253 | Anderson et al. | Jan 2015 | B2 |
8992260 | Coffey et al. | Mar 2015 | B2 |
9020319 | Anderson et al. | Apr 2015 | B2 |
9054440 | Taylor et al. | Jun 2015 | B2 |
9075203 | Holmberg | Jul 2015 | B2 |
9140859 | Anderson et al. | Sep 2015 | B2 |
9176294 | Smrha et al. | Nov 2015 | B2 |
9198320 | Anderson et al. | Nov 2015 | B2 |
9213363 | Anderson et al. | Dec 2015 | B2 |
9223105 | Anderson et al. | Dec 2015 | B2 |
9244229 | Petersen | Jan 2016 | B2 |
9265172 | Anderson et al. | Feb 2016 | B2 |
9401552 | Coffey et al. | Jul 2016 | B2 |
9417399 | Anderson et al. | Aug 2016 | B2 |
9470742 | Coffey et al. | Oct 2016 | B2 |
20020008613 | Nathan et al. | Jan 2002 | A1 |
20020081076 | Lampert et al. | Jun 2002 | A1 |
20030031423 | Zimmel | Feb 2003 | A1 |
20030060081 | Yasuda | Mar 2003 | A1 |
20030236018 | Mimoto et al. | Dec 2003 | A1 |
20040052471 | Colombo | Mar 2004 | A1 |
20040052498 | Colombo et al. | Mar 2004 | A1 |
20040117515 | Sago et al. | Jun 2004 | A1 |
20040240807 | Frohlich et al. | Dec 2004 | A1 |
20050215119 | Kaneko | Sep 2005 | A1 |
20050249477 | Parrish | Nov 2005 | A1 |
20060160395 | Macauley et al. | Jul 2006 | A1 |
20060193591 | Rapp et al. | Aug 2006 | A1 |
20060228086 | Holmberg et al. | Oct 2006 | A1 |
20070116411 | Benton et al. | May 2007 | A1 |
20070237470 | Aronson et al. | Oct 2007 | A1 |
20070254529 | Pepe et al. | Nov 2007 | A1 |
20080090450 | Harano et al. | Apr 2008 | A1 |
20080090454 | Hoath et al. | Apr 2008 | A1 |
20080100456 | Downie et al. | May 2008 | A1 |
20080100467 | Downie et al. | May 2008 | A1 |
20080175532 | Ruckstuhl et al. | Jul 2008 | A1 |
20080175550 | Coburn et al. | Jul 2008 | A1 |
20090034911 | Murano | Feb 2009 | A1 |
20090097846 | Kozischek 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 |
20100048064 | Peng | Feb 2010 | A1 |
20100079248 | Greveling et al. | 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 |
20100303421 | He et al. | Dec 2010 | A1 |
20110043371 | German et al. | Feb 2011 | A1 |
20110115494 | Taylor et al. | May 2011 | A1 |
20110116748 | Smrha et al. | May 2011 | A1 |
20110221601 | Aguren | Sep 2011 | A1 |
20110222819 | Anderson et al. | Sep 2011 | A1 |
20110235979 | Anderson et al. | Sep 2011 | A1 |
20110255829 | Anderson et al. | Oct 2011 | A1 |
20110262077 | Anderson et al. | Oct 2011 | A1 |
20120003877 | Bareel et al. | Jan 2012 | A1 |
20120021636 | Debendictis et al. | Jan 2012 | A1 |
20120208401 | Petersen | Aug 2012 | A1 |
20140038462 | Coffey et at | Feb 2014 | A1 |
20140219656 | Lawson et al. | Aug 2014 | A1 |
20140286610 | Anderson et al. | Sep 2014 | A1 |
20150270662 | Taylor et al. | Sep 2015 | A1 |
20160054528 | Smrha et al. | Feb 2016 | A1 |
20160154423 | Anderson et al. | Jun 2016 | A1 |
20160192527 | Anderson et al. | Jun 2016 | A1 |
20160212876 | Anderson et al. | Jul 2016 | A1 |
Number | Date | Country |
---|---|---|
2499803 | Apr 2004 | CA |
101968558 | Feb 2011 | CN |
102 44 304 | Mar 2004 | DE |
10 2004 033 940 | Feb 2006 | DE |
1 199 586 | Apr 2002 | EP |
1 237 024 | Sep 2002 | EP |
1 467 232 | Oct 2004 | EP |
1 662 287 | May 2006 | EP |
2-33110 | Feb 1990 | JP |
4-72488 | Jun 1992 | JP |
4-174406 | Jun 1992 | JP |
10-64638 | Mar 1998 | JP |
2004-29162 | Jan 2004 | JP |
WO 0065696 | Nov 2000 | WO |
WO 0239551 | May 2002 | WO |
WO 0247215 | Jun 2002 | WO |
WO 2007061490 | May 2007 | 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. |
FOCIS 10—Fiber Optic Connector Intermateability Standard—Type LC, TIA/EIA-604-10A, 38 pages (Mar. 2002). |
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 mailed May 23, 2011 in related Application No. PCT/US2011/024650 (17 pages). |
International Search Report and Written Opinion mailed Sep. 12, 2011 in related Application No. PCT/US2011/024652 (28 pages). |
International Search Report and Written Opinion mailed Sep. 19, 2011 in related Application No. PCT/US2011/024649 (27 pages). |
International Search Report and Written Opinion mailed Sep. 22, 2011 in related Application No. PCT/US2011/024653 (25 pages). |
International Search Report and Written Opinion for PCT/US2013/053441 mailed Dec. 16, 2013. |
iTRACS Physical Layer Manager FAQ, obtained on Jun. 11, 2008 from http://www.itracs.com/products/physical-layer-manager-faqs.html (6 pages). |
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). |
Partial International Search Report and Invitation to Pay Additional Fees mailed May 19, 2011 in related Application No. PCT/US2011/024653 (6 pages). |
Partial International Search and Invitation to Pay Additional Fees mailed Jun. 8, 2011 in related Application No. PCT/US2011/024649 (8 pages). |
Partial International Search and Invitation to Pay Additional Fees mailed Jun. 16, 2011 in related Application No. PCT/US2011/024652 (9 pages). |
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 | |
---|---|---|---|
20160131858 A1 | May 2016 | US |
Number | Date | Country | |
---|---|---|---|
61303961 | Feb 2010 | US | |
61413828 | Nov 2010 | US | |
61437504 | Jan 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13025784 | Feb 2011 | US |
Child | 14860175 | US |