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.
In accordance with some aspects of the disclosure, an optical adapter block assembly includes an adapter block, a circuit board arrangement, and a cover. The adapter block defines ports and apertures associated with the ports. Contact assemblies can be disposed in the apertures of the adapter block so that portions of each contact assembly extend into an interior of the adapter block. The circuit board arrangement has a first side including circuit board components and a second side configured to seat on the adapter block. The second side also is configured to electrically connect to the contact assemblies disposed in the apertures of the adapter block. The cover is configured to seat on the first side of the circuit board arrangement. The cover is attached to the adapter block so that the circuit board arrangement is held to the adapter block by the cover.
In certain examples, the cover is latched to the adapter block. In certain examples, the cover is heat staked to the adapter block.
In accordance with other aspects of the disclosure, an optical adapter block assembly includes a first adapter block, a second adapter block, and a connecting member that couples to a first side of the first adapter block and to a second side of the second adapter block to hold the first and second adapter blocks together as a unit. The first adapter block defines front ports at a front of the first adapter block and a rear ports at a rear of the first adapter block. The top of the first adapter block defines an aperture for each port of the first adapter block. The second adapter block defines front ports at a front of the second adapter block and rear ports at a rear of the second adapter block. The top of the second adapter block defines an aperture for each port of the second adapter block.
In accordance with other aspects of the disclosure, an optical adapter block assembly includes an adapter block, a circuit board arrangement, and a cover that is heat staked to the adapter block. The adapter block defines front and rear ports. The adapter block also defines apertures at a top of the adapter block with each aperture being associated with one of the front ports or rear ports. The adapter block also includes heat stakes extending upwardly from the top of the adapter block. The circuit board arrangement defines openings through which the heat stakes pass when the circuit board arrangement is disposed on the adapter block. The cover includes a top plate from which wells extend downwardly. The wells define through-holes and counter-bores through which the heat stakes extend when the cover is mounted to the adapter block. A tip of each heat stake is configured to be melted into the counter-bore of the respective well to secure the cover plate and the circuit board arrangement to the adapter block.
In certain examples, the heat stakes are positioned adjacent the apertures in the adapter block to hold the circuit board securely to the adapter block in the location of the apertures. Contact assemblies can be mounted in the apertures. Positioning the heat stakes at the apertures inhibits movement of the circuit board away from the adapter at the apertures that may otherwise be caused by deflection of the contact assemblies within the apertures.
A variety of additional inventive aspects will be set forth in the description that follows. The inventive aspects can relate to individual features and to combinations of features. It is to be understood that both the forgoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the broad inventive concepts upon which the embodiments disclosed herein are based.
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:
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.
In general, media segments connect equipment of the communications network. Non-limiting examples of media segments include optical cables, electrical cables, and hybrid cables. This disclosure will focus on optical media segments. The media segments may be terminated with optical plug connectors, media converters, or other optical termination components.
The adapter block assembly 110 includes a fiber optic adapter defining at least one connection opening 111 having a first port end 112 and a second port end 114. A sleeve (e.g., a split sleeve) 103 is arranged within the connection opening 111 of the adapter 110 between the first and second port ends 112, 114. Each port end 112, 114 is configured to receive a connector arrangement 120. Each fiber connector arrangement 120, 130 includes a ferrule 124, 134 through which optical signals from the optical fiber 122, 132, respectively, pass. The ferrules 124, 134 are held and aligned by a sleeve 103 to allow optical signals to pass between the ferrules 124, 134. The aligned ferrules 124, 134 of the connector arrangements 120, 130 create an optical path along which the communication signals may be carried.
In accordance with aspects of the disclosure, the communications network is coupled to or incorporates a data management system that 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 communications network. 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 communications network (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 network. Physical layer information of the communications network can include media information, device information, and location information. Media information refers to physical layer information pertaining to cables, plugs, connectors, and other such physical media. Non-limiting examples of media information include a part number, a serial number, a plug type, a conductor type, a cable length, cable polarity, a cable pass-through capacity, a date of manufacture, a manufacturing lot number, the color or shape of the plug connector, an insertion count, and testing or performance information. 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. Location information refers to physical layer information pertaining to a physical layout of a building or buildings in which the network is deployed.
In accordance with some aspects, one or more of the components (e.g., media segments, equipment, etc.) of the communications network are configured to store physical layer information pertaining to the component as will be disclosed in more detail herein. Some components include media reading interfaces that are configured to read stored physical layer information from the components. The physical layer information obtained by the media reading interface may be communicated over the network for processing and/or storage.
For example, the adapter block assembly 110 of
In one implementation, each of the storage devices 125, 135 is implemented using an EEPROM (e.g., a PCB surface-mount EEPROM). In other implementations, the storage devices 125, 135 are implemented using other non-volatile memory device. Each storage device 125, 135 is arranged and configured so that it does not interfere or interact with the communications signals communicated over the media segments 122, 132.
In accordance with some aspects, the adapter 110 is coupled to at least a first media reading interface 116. In certain implementations, the adapter 110 also is coupled to at least a second media interface 118. In certain implementations, the adapter 110 is coupled to multiple media reading interfaces. In an example, the adapter 110 includes a media reading interface for each port end defined by the adapter 110. In another example, the adapter 110 includes a media reading interface for each connection opening 111 defined by the adapter 110. In other implementations, the adapter 110 can include any desired number of media reading interfaces 116, 118.
In some implementations, at least the first media reading interface 116 is mounted to a printed circuit board 115. In some implementations, the printed circuit board 115 also can include the second media reading interface 118. The printed circuit board 115 of the adapter 110 can be communicatively connected to one or more programmable processors and/or to one or more network interfaces (see data line 119 of
When the first connector arrangement 120 is received in the first port end 112 of the adapter 110, the first media reading interface 116 is configured to enable reading (e.g., by an electronic processor) of the information stored in the storage device 125. The information read from the first connector arrangement 120 can be transferred through the printed circuit board 115 to the physical layer data management network. When the second connector arrangement 130 is received in the second port end 114 of the adapter 110, the second media reading interface 118 is configured to enable reading (e.g., by an electronic processor) of the information stored in the storage device 135. The information read from the second connector arrangement 130 can be transferred through the printed circuit board 115 or another circuit board to the physical layer data management network.
In some such implementations, the storage devices 125, 135 and the media reading interfaces 116, 118 each include at least three (3) leads—a power lead, a ground lead, and a data lead. The three leads of the storage devices 125, 135 come into electrical contact with three (3) corresponding leads of the media reading interfaces 116, 118 when the corresponding media segment is inserted in the corresponding port. In other 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 125, 135 and the media reading interfaces 116, 118 may each include four (4) leads, five (5) leads, six (6) leads, etc.
One example contact assembly 160 suitable for implementing any of the media reading interfaces 116, 118 of
Additional information about how physical layer information can be read from the plug connectors by the contact assemblies at adapters can be found in U.S. Publication No. 2011-0262077, the disclosure of which is hereby incorporated herein by reference.
In some implementations, the contact assembly 160 includes a sensing contact 166 that extends outwardly from the body 161. A first of the contacts 162 includes an extension 164 that aligns with the sensing contact 166. When the optical connector 150 is spaced from the contact assembly 160, the extension 164 is spaced from the sensing contact 166 (
In some implementations, the contact assembly body 161 is configured to be secured at an aperture defined in an adapter block. In other implementations, the contact assembly body 161 is configured to be secured to a circuit board or other surface. For example, in certain implementations, the body 161 can include one or more pegs 168 that extend outwardly from the body 161 to be received in apertures defined in the surface. In the example shown, the body 161 defines two pegs 168 extending away from the contact sections 163. In certain implementations, the contact assembly body 161 defines a tapered section 169 that accommodates deflection of the contacts 162 (e.g., when an optical connector 150 engages the contact assembly 160.
Further details regarding one example contact assembly suitable for use as contact assembly 160 are shown and described in copending U.S. Provisional Application No. 61/843,752, filed Jul. 8, 2013, and titled “Optical Assemblies with Managed Connectivity,” the disclosure of which is hereby incorporated herein by reference.
In accordance with some aspects of the disclosure, one or more contact assemblies 160 can be mounted to an adapter block assembly.
Additional information about adapter blocks or other connector assemblies having staggered configurations can be found in U.S. Publication No. 2013-0183018, filed Jan. 9, 2013, and titled “Fiber Optic Adapter Block,” the disclosure of which is hereby incorporated herein by reference.
As shown in
A contact assembly 160 is disposed between the adapter block 210 and the circuit board 230. A right contact assembly 160 corresponds with the right port 212 and a left contact assembly 160 corresponds with the left port 212. Contacts 162 of the contact assembly 160 extend through apertures 215 in the adapter block 210. The contacts 162 are positioned and oriented so that the contact sections 163 align with the contact region 152 of optical connectors 150 received at corresponding ports 212. Pegs 168 extend into the circuit board 230.
In some implementations, the circuit board 230 is mounted flush with the adapter block 210. For example, in certain implementations, the circuit board 230 can be mounted within a recessed area 214 of the adapter block 210 between end sections 218 (e.g., see
Referring back to
In certain implementations, the periphery of the cover 240 seats on only portions of the end sections 218. For example, the periphery of the cover 240 can be recessed inwardly from the ports 212 to enhance access to the ports 212. In an example, the periphery of the cover 240 can be recessed inwardly from the front and rear curved portions 216. In some implementations, the cover 240 can define ramped or tapered sections 245 at the front and rear of the cover 240. The tapered sections 245 further enhance access to the ports 212 by reducing the material that might otherwise block finger access to the ports 212 when the cover 240 is mounted to the adapter block 210.
In some implementations, the front ports 212 are located generally flush relative to each other. In other implementations, however, a perimeter of the adapter block 210 can have a staggered configuration so that some of the front ports 212 are offset forwardly/rearwardly along the insertion axes relative to others of the front ports 212. In one example, adjacent front ports 212 are forwardly/rearwardly offset from each other. In the example shown, sections of the adapter block 210 are forwardly/rearwardly offset from each other. For example, a first section 213A of the adapter block 210 is offset rearwardly relative to a second section 213B of the adapter block 210 (see
In some implementations, the adapter block 210 is configured to be coupled to one or more adapter blocks 210 and/or to be coupled to a tray, blade, drawer, tray, or other such structure (hereinafter “tray”). In certain implementations, each adapter block 210 includes an engagement member 217 that extends outwardly from at least one side 205, 206 of the adapter block 210. In an example, an engagement member 217 extends outwardly from both sides 205, 206 of the adapter block 210. In certain implementations, the engagement member 217 has a T-shaped profile when viewed from above or below the adapter block 210. For example, the engagement member 217 can have a first portion 217a extending outwardly from the side 205, 206 of the adapter block 210 and a second portion 217b extending generally orthogonally across the first portion 217a (
Referring to
Each cavity 222 is accessible through an open bottom of the joining member 220 (
In some implementations, a latching hook 225 extends downwardly within each of the cavities 222 of the joining member 220. For example, in
The circuit board 230 shown in
The latching fingers 256 are configured to engage the adapter block assembly 200 (e.g., the joining member 220) to further secure the adapter block assembly 200 to the tray 250. In certain implementations, two latching fingers 256 face in opposite directions towards the side rails 251, 252. In certain implementations, the latching fingers 256 extend upwardly through the cavities 222 defined in the joining member 220 and through the apertures 224 defined at the top of the joining member 220 to latch over the top of the joining member 220. In other implementations, the latching members 256 latch over shoulders defined within the joining member 220. In still other implementations, another type of adapter block assembly securement structure can be disposed at the mounting rail 254.
Mounting structures 255 are provided at the inner sides of the side rails 251, 252. In certain implementations, the mounting structures 255 are laterally aligned. The mounting structures 255 are configured to receive the engagement members 217 of the adapter blocks 217. For example, the mounting structures 255 receive the engagement members 217 extending outwardly from the sides 205, 206 of the adapter block assembly 200. In an example, each mounting structures 255 defines a T-shaped cavity having an open top through which an engagement member 217 can slide. Each mounting structures 255 also includes a shelf on which the engagement member 217 can seat.
In certain implementations, the tray 250 is moveable (e.g., slideable, pivotal, etc.) relative to a rack, cabinet, or other mounting structure. For example, exterior surfaces of the side rails 251, 252 can include guides 258 that interact with guides on the holding structure. In certain implementations, the tray 250 includes cable management guides 259 that form routing paths for optical fibers/cables routed onto the tray 250. The management guides 259 may aid in managing the optical fibers/cables during movement of the tray 250.
In some implementations, the tray 250 provides an electrical connection between the adapter block assembly 200 and a data management network. In some implementations, an electrical circuit (e.g., a second circuit board) is mounted to the mounting rail 254. For example, the mounting rail 254 and/or one or more of the cross-members 253 can define a pocket or channel sized to fit the circuit board (e.g., see
In other implementations, an electrical cable (e.g., a flexible cable) or other circuit can extend from the chassis electrical circuit, through the aperture in the second side rail 252, extend across at least part of the cross-members 253, and connect to the second circuit board. A cover can be positioned over the cross-member channel to protect the flex circuit. In an example, the cover can be latched (e.g., using latches 256) other otherwise secured to the cross-member 253. In certain implementations, the chassis electrical circuit includes a local processor to manage the data obtained from the adapter block assembly 200. In other implementations, the chassis electrical circuit includes a data port through which the data can be carried to a data management network.
As shown in
Contact assemblies 160 and circuit board components 334 (e.g., memory) are mounted to the circuit board 330. For example, at least some of the components 334 can be mounted to a first side 331 of the circuit board 330 and the contact assemblies 160 can be mounted to a second side 332 of the circuit board 330. The contact assemblies 160 face towards the adapter blocks 310A, 310B when the circuit board 330 is disposed between the adapter blocks 310 and the covers 340. The covers 340A, 340B extends over at least some of the components 334 of the circuit board 330. In some implementations, the covers 340A, 340B are secured to the adapter blocks 310A, 310B, thereby holding the circuit board 330 therebetween.
In some implementations, the front ports 312 are located generally flush relative to each other. In other implementations, however, a perimeter of the adapter block 310 can have a staggered configuration so that some of the front ports 312 are offset forwardly/rearwardly along the insertion axes relative to others of the front ports 312. In one example, adjacent front ports 312 are forwardly/rearwardly offset from each other. In the example shown, sections of the adapter block 310 are forwardly/rearwardly offset from each other. For example, a first section 313A of the adapter block 310 is offset rearwardly relative to an adjacent second section 313B of the adapter block 310 (see
The top of the adapter block 310 defines the recessed area 314 between a front end section 318 and a rear end section 318. The recessed area 314 enables the circuit board 330 to be flush mounted with the adapter block 310. For example, a circuit board 330 mounted in the recessed area 314 would lie flush with a top of the front and rear end sections 318. Apertures 315 are defined in the recessed area 314 and extend into a hollow interior of the adapter block 310. The contact assemblies 160 of the circuit board 330 extend through the apertures 310 when the circuit board 330 is disposed at the recessed area 314. In certain implementations, the adapter block 310 defines front and rear curved sections 316 that extend downwardly from the end sections 318 and outwardly to define the front and rear ports 312.
The adapter block 310 is configured to latch to the cover 340. For example, in some implementations, the adapter block 310 can include latch arms 361 that extend upwardly from a top of the adapter block 310. The latch arms 361 include latch hooks 362 that extend outwardly from the latch arms 361. In the example shown, a front latch arm 361 and a rear latch arm 361 extend upwardly at each section 313 of the adapter block 310 (see
The cover 340 also defines through-openings 347 that extend through the first and second surfaces 341, 342 of the cover 340. The through-openings 347 are wider than the latch arms 361. The cover 340 also defines platforms 348 adjacent the through-openings 347. As shown in
As seen in
In some implementations, the adapter block 310 is configured to be coupled to one or more adapter blocks 310 and/or to be coupled to a tray (e.g., tray 250 of
In certain implementations, the engagement member 317 has an H-shaped profile when viewed from the side 305, 306 the adapter block 310. For example, the engagement member 317 can have a two L-shaped flanges 317a extending outwardly from the side 305, 306 of the adapter block 310; a shelf 317b extending between the flanges 317a, and a ramp or tapered section 317c extending inwardly from the shelf 317b towards the side 305, 306 of the adapter block 310. The L-shaped flanges 317a face forwardly and rearwardly of the adapter block 310 (see
Referring to
Sidewalls of the body 321 define one or more receiving slots 323 that are sized to receive the engagement members 317 of the adapter blocks 310. In the example shown in
In some implementations, the joining member 320 also includes a latching arm 324 that extends upwardly within one or more of the receiving slots 323. The latching arm 324 includes a latching hook 325 that extends outwardly from the arm 324. When the engagement member 317 of the adapter block 310 is slit into the receiving slot 323, the ramp 317c of the engagement member 317 cams against the latching hook 325 to deflect the arm 324 inwardly until the latching hook 325 clears the shelf 317b. The arm 324 returns to its initial position so that the latching hook 325 catches on the shelf 317b. The latching arm 324 inhibits the adapter block 310 from being slid out of engagement with the joining member 320.
In some implementations, opposite sides of the joining member 320 each define a second slot 326 adjacent the receiving slot 323. The second slot 326 does not extend fully through the side of the joining member 320. The second slot 326 is sized to receive the stop member 319 when the adapter block engagement member 317 is slid into the receiving slot 323. Interaction between the second slot 326 and the stop member 319 inhibits the adapter block 310 from sliding all the way through the joining member 320. In some implementations, the joining body 321 also includes protrusions 329 that extend outwardly from the body 321 adjacent the receiving slots 323. For example, the protrusions 329 can be disposed beneath the receiving slots 323 at the sidewalls. In certain implementations, the adapter blocks 310 may seat on the protrusions 329 to inhibit movement of the adapter blocks 310 past the joining member 320.
In some implementations, the joining member 320 includes a retention member 328 disposed at each of the first and second open ends of the body 321. For example, each retention member 328 can be formed at a top of the body 321 and face out towards the respective end opening 322. In certain implementations, the retention member 328 can be inwardly recessed into the top of the body 321 relative to the open end of the body 321.
Referring now to
The adapter block 410 includes a body 411 defining a plurality of front and rear connector ports 412. The adapter body 411 includes some sections 413 that are offset forwardly or rearwardly relative to other sections 413. For example, a first section 413A shown in
A top of the adapter block 410 defines apertures 415 at which contact assemblies 160 can be mounted. In some implementations, a contact assembly 160 is disposed at each port 412. In other implementations, a contact assembly 160 can be disposed at alternate ports 412 and/or at the ports 412 on only the front or rear of the adapter block 410. Heat stakes 416 extend upwardly from the top of the adapter block 410. In the example shown, a front heat stake 416 and a rear heat stake 416 extend upwardly at each section 413 of the adapter block 410 except for the intermediate portion 414. In other implementations, the adapter block 410 can include any desired number of heat stakes 416.
The circuit board 430 includes a board body 431 on which electrical components 432 can be mounted. The circuit board body 431 also is configured to electrically couple to the contact assemblies 160 (e.g., via contact pads). The board body 431 defines openings 433 through which the heat stakes 416 extend when the circuit board 430 is seated on the adapter block 410.
The cover 440 is configured to extend over the circuit board 430 and to attach to the adapter block 410. The cover 440 includes a top plate 441 from which tabs 442 extend downwardly. The tabs 442 are configured to seat on the circuit board 430.
For example, in some implementations, the tabs 442 are configured to seat on the board body 431 (see
The cover 440 defines through-holes 443 that extend through the top plate 441 of the cover 440. The through-holes 443 are defined through wells 444 extending downwardly from the top plate 441. The through-holes 443 are sized to accommodate passage of the heat stakes 416 of the adapter blocks 410 when the circuit board 430 and cover 440 are mounted to the adapter block 410. The wells 444 define counter-bores 445 leading to the exterior surface of the top plate 441. The counter-bores 445 are frustro-conical portions of the through-hole 443 that taper away from the heat stakes 416. In certain implementations, the heat stakes 416 are sized to extend beyond the top plate 441 of the cover 440.
To secure the adapter block assembly 400 together, the tips of the heat stakes 416 are melted. The melted heat stakes 416 at least partially fill the counter-bores 445. In some implementations, the melted heat stakes 416 are generally flush with the exterior surface of the cover top plate 441. In other implementations, the melted heat stakes 416 can be recessed inwardly or can protrude outwardly from the cover top plate 441. In certain implementations, the melted heat stake material filling the counter-bores 445 does not fit through the wells 444, thereby inhibiting removal of the cover 440 from the adapter block 410. For example, the melted material may have a frustro-conical shape or other shape having a maximum cross-dimension that is greater than an internal cross-dimension of the well 444. In certain implementations, the melted heat stake material fuses or otherwise bonds to the material forming the cover 440 to inhibit removal of the cover 440 from the adapter block 410.
In some implementations, the heat stakes 416 are positioned adjacent the contact assemblies 160 (e.g., adjacent the apertures 415) mounted to the adapter block 410. Accordingly, the bond between the cover 440 and the adapter block 410 is strongest near the contact assemblies 160. These bonds facilitate holding the cover 440 and hence the circuit board 430 against the adapter block 410 despite any deflection of the contact assembly 160 (e.g., the sensing contact 166) against the circuit board 430. Maintaining the position of the circuit board 430 even during deflection of the contact assembly 160 enhances the connection between the electrical contacts 162 of the contact assembly 160 and contact pads on the circuit board 430.
The fourth example adapter block assembly 500 includes an adapter block 510, a circuit board 530, and a cover 540. In the example shown, each of these three components 510, 530, 540 is formed from as a single-piece unit. In other implementations, however, any of these components 510, 530, 540 could be formed from multiple pieces (e.g., multiple adapter blocks with joining members, multiple circuit boards, multiple cover pieces, etc.).
The adapter block 510 includes a body 511 defining a plurality of front and rear connector ports 512. The adapter body 511 includes some sections 513 that are offset forwardly or rearwardly relative to other sections 513. For example, a first section 513A shown in
A top of the adapter block 510 defines apertures 515 at which contact assemblies 160 can be mounted. In some implementations, a contact assembly 160 is disposed at each port 512. In other implementations, a contact assembly 160 can be disposed at alternate ports 512 and/or at the ports 512 on only the front or rear of the adapter block 510. Heat stakes 516 extend upwardly from the top of the adapter block 510. In the example shown, a front heat stake 516 and a rear heat stake 516 extend upwardly at each section 513 of the adapter block 510 except for the intermediate portion 514. In other implementations, the adapter block 510 can include any desired number of heat stakes 516.
In some implementations, the adapter block 510 can be configured to mount to a tray (e.g., tray 250 of
The circuit board 530 includes a board body 531 on which electrical components 532 can be mounted. The circuit board body 531 also is configured to electrically couple to the contact assemblies 160 (e.g., via contact pads). The board body 531 defines openings through which the heat stakes 516 extend when the circuit board 530 is seated on the adapter block 510. The board body 531 also includes an intermediate portion 534 that is configured to extend over the intermediate portion 514 of the adapter block 510. A circuit board connector 535 can extend downwardly from the circuit board body 531 and through an aperture 518 defined in the intermediate portion 514 of the adapter block 510 to connect to an electrical circuit disposed beneath the adapter block 510.
The cover 540 is configured to extend over the circuit board 530 and to attach to the adapter block 510. The cover 540 includes a top plate 541 from which sidewalls 542 extend downwardly. The sidewalls 542 are configured to seat on the circuit board 430. For example, in some implementations, the sidewalls 542 are configured to seat on the board body 530. In other implementations, the sidewalls 542 can be configured to seat on components 532 of the circuit board 430. The sidewalls 542 raise the top plate 541 sufficiently far off the circuit board 530 to accommodate the circuit board components 532 beneath he top plate 541. In certain implementations, tabs 547 also extend downwardly from the top plate 541 to hold the top plate 541 off the circuit board 530. In certain implementations, the sidewalls 542 define apertures 546 that lead to a hollow interior of the cover 540. The apertures 546 enable light from indicators (e.g., LEDs) mounted to the circuit board 530 to shine through and indicate an adapter port 512.
The cover 540 defines through-holes 543 that extend through the top plate 541. The through-holes 543 are defined through wells 544 extending downwardly from the top plate 541 (see
To secure the components 510, 530, 540 of the adapter block assembly 500 together, the tips of the heat stakes 516 are melted. The melted tips at least partially fill the counter-bores 545. In some implementations, the melted heat stakes 516 are generally flush with the exterior surface of the cover top plate 541. In other implementations, the melted heat stakes 516 can be recessed inwardly or can protrude outwardly from the cover top plate 541. In certain implementations, the melted heat stake material filling the counter-bores 545 does not fit through the wells 544, thereby inhibiting removal of the cover 540 from the adapter block 510. For example, the melted material may have a frustro-conical shape or other shape having a maximum cross-dimension that is greater than an internal cross-dimension of the well 544. In certain implementations, the melted heat stake material fuses or otherwise bonds to the material forming the cover 540 to inhibit removal of the cover 540 from the adapter block 510.
In accordance with some aspects of the disclosure, some of the adapter block assemblies disclosed above have heights of no more than 13 mm including the adapters, the contact assemblies, the circuit board assemblies, and any cover assembly or housing assembly. For example, some of the adapter block assemblies have heights of no more than 12.75 mm. Certain of the adapter block assemblies have heights of no more than 12.5 mm. In an example, certain of the adapter block assemblies have heights of no more than 12.55 mm. In certain implementations, the adapter assemblies by themselves can have heights of no more than 9.5 mm. In an example, certain of the adapter block assemblies by themselves can have heights of no more than 9.35 mm. In certain implementations, the adapter assemblies by themselves can have heights of no more than 9 mm. In certain implementations, the adapter assemblies by themselves can have heights of no more than 8.5 mm. In certain implementations, the adapter assemblies by themselves can have heights of no more than 8 mm.
In the example shown in
The mounting rail 614 defines a pocket 617 at which the circuit board 620 can be mounted. Connection members 622 are mounted to the circuit board 620 in alignment with circuit board contact members of the adapter block assembly to be mounted to the tray 610. The circuit board 620 also includes a connection member 625 at a cross-member 613. In certain implementations, at least part of the cross-member 613 can also define part of the pocket 617. At least a portion 632 of the flexible cable 630 can be routed through the second side rail 612, through the pocket 617 along the cross-member 613, to the connection member 625 of the circuit board 620. A cover 618 can be mounted to the cross-member 613 to cover (e.g., protect) the flexible cable portion 632.
An opposite end 636 of the flexible cable is routed to or through the side plane 640. The side plane 640 defines one or more guide slots 642 along which the tray 610 can slide. For example, one of the side rails 611, 612 of the tray 610 can slide along one of the guide slots 642. The flexible cable 630 includes an intermediate length 634 that extends between the side rail 612 of the tray 610 and the side plane 640. The intermediate length 634 is folded back on itself to accommodate movement of the tray 610 relative to the side plane 640.
Information about how such trays (e.g., trays 610) can be moveably mounted within a chassis or rack and how such an arrangement can be used within a telecommunications system can be found in copending U.S. application Ser. No. 14/169,941, filed Jan. 31, 2014, and titled “Slidable Telecommunications Tray with Cable Slack Management,” and having attorney docket number 02316.3597USU1, the disclosure of which is hereby incorporated herein by reference. Another system including trays on which the adapter blocks and cassettes disclosed herein can be mounted is disclosed in copending U.S. application Ser. No. 13/925,375, filed Jun. 24, 2013, and titled “Slidable Fiber Optic Connection Module with Cable Slack Management,” the disclosure of which is hereby incorporated herein by reference.
The fifth example adapter block assembly 700 includes at least one adapter block arrangement 710, a circuit board 730 (
The circuit board 730 shown in
In some implementations, the joining member 720 includes a shroud 727 through which pins of the connector 735 extend. The shroud 727 inhibits damage (e.g., bending, breaking, etc.) to the pins when the adapter block arrangement 710 is being mounted to the tray arrangement 600 or other mounting surface. In certain implementations, the joining member 720 includes two shrouds 727 (e.g., a forward shroud and a rearward shroud). The shrouds 727 accommodate multiple connectors on the tray 610. In an example, the pin connector 735 extends through the forward shroud 727 and into a first of two female connectors on the tray 610 and a second of the female connectors is received in the rearward shroud 727. In another example, the adapter block assembly 700 is rotated 180° relative to the tray 610 so that the pin connector 735 extends through the forward shroud 727 and into the second female connector on the tray 610 and the first female connector is received in the rearward shroud 727.
The cover arrangement 740 includes a first cover 740A, a second cover 740B, and an intermediate cover 750. The first and second covers 740A, 740B are disposed over the circuit board 730 and coupled to the adapter blocks 710A, 710B as will be disclosed in more detail herein. The intermediate cover 750 extends over an intermediate portion 736 (
Referring to
The cover 740 that is configured to receive the latch arms 761 to secure the cover 740 to the adapter block arrangement 710. The cover 740 also defines through-openings 747 that extend through the cover 740. Each through-opening 747 includes a first portion and a second portion. The first portion is sized to enable the latch hook 762 of the latch arm 761 to pass therethrough. The second portion is sized to inhibit passage of the latch hook 762 therethrough. The cover 740 also defines a platform 748 adjacent the second portion of each through-openings 747.
The first cover piece 740A is mounted to the first adapter block 710A by pressing the first cover piece 740A onto the first adapter block 710A (see
The second cover piece 740B is mounted to the second adapter block 710B using the same process, but sliding the second cover piece 740B in a second direction D2 that is opposite the first direction D1 (see
In the example shown, the intermediate cover 750 includes a body 751 defining latching slots 752 that align with latch arms 722 on the joining member 720. The latch arms 722 snap into the latching slots 752 when the intermediate cover 750 is positioned over the intermediate portion 736 of the circuit board, which seats on the joining member 720. In other implementations, the intermediate cover 750 can otherwise be coupled to the adapter block 710.
In some implementations, the adapter block assembly 700 is configured to be coupled to a tray (e.g., tray 250 of
In certain implementations, the joining member 720 includes latch fingers 725 configured to latch to the engagement members 717 of adapter blocks 710. For example, a joining member 720 may have a first latch finger that hooks to the engagement member at a first side 705 of a first adapter block 710A and a second latch finger 725 that hooks to the engagement member 717 at a second side 706 of a second adapter block 710B. In certain examples, the joining member 720 couples the adapter blocks 710A, 710B together so that front ports 712 of the adapter blocks 710A, 710B extend along a common plane.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention 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 application Ser. No. 16/388,983, filed Apr. 19, 2019, now U.S. Pat. No. 10,746,943, which is a continuation of application Ser. No. 15/722,648, filed Oct. 2, 2017, now U.S. Pat. No. 10,268,000, which is a continuation of application Ser. No. 15/065,338, filed Mar. 9, 2016, now U.S. Pat. No. 9,778,424, which is a continuation of application Ser. No. 14/169,912, filed Jan. 31, 2014, now U.S. Pat. No. 9,285,552, which application claims the benefit of provisional application Ser. No. 61/843,718, filed Jul. 8, 2013, and titled “Optical Assemblies with Managed Connectivity;” and of provisional application Ser. No. 61/761,034, filed Feb. 5, 2013, and titled “Optical Assemblies with 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 |
5107075 | Currier, Jr. | Apr 1992 | 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 |
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 |
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 |
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 |
7073953 | Roth et al. | Jul 2006 | B2 |
7077710 | Haggay 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 et al. | Jun 2007 | B1 |
7234944 | Nordin et al. | Jun 2007 | B2 |
7241157 | Zhuang et al. | Jul 2007 | B2 |
7297018 | Caveney et al. | Nov 2007 | B2 |
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 | 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 |
8157582 | Frey et al. | Apr 2012 | B2 |
8282425 | Bopp et al. | Oct 2012 | B2 |
8287316 | Pepe et al. | Oct 2012 | B2 |
8596882 | Smrha et al. | Dec 2013 | B2 |
8690593 | Anderson et al. | Apr 2014 | B2 |
9128262 | Campbell et al. | Sep 2015 | B2 |
9285552 | Marcouiller | Mar 2016 | B2 |
9778424 | Marcouiller et al. | Oct 2017 | B2 |
10268000 | Marcouiller et al. | Apr 2019 | B2 |
10746943 | Marcouiller | Aug 2020 | B2 |
20020008613 | Nathan et al. | Jan 2002 | A1 |
20020081076 | Lampert et al. | Jun 2002 | A1 |
20030031423 | Zimmel | Feb 2003 | A1 |
20040052471 | Colombo et al. | Mar 2004 | A1 |
20040052498 | Colombo et al. | Mar 2004 | A1 |
20040117515 | Sago et al. | Jun 2004 | A1 |
20040240807 | Frohlich et al. | Dec 2004 | A1 |
20050165710 | Givaty | Jul 2005 | A1 |
20050249477 | Parrish | Nov 2005 | A1 |
20060009061 | Machado et al. | Jan 2006 | A1 |
20060141871 | Sakamoto | Jun 2006 | 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 |
20090166404 | German et al. | Jul 2009 | A1 |
20090215310 | Hoath et al. | Aug 2009 | A1 |
20090232455 | Nhep | Sep 2009 | A1 |
20100048064 | Peng | Feb 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 |
20110085774 | Murphy et al. | Apr 2011 | A1 |
20110092100 | Coffey et al. | Apr 2011 | A1 |
20110115494 | Taylor et al. | May 2011 | A1 |
20110116748 | Smrha et al. | May 2011 | A1 |
20110222819 | Anderson et al. | Sep 2011 | A1 |
20110235979 | Anderson et al. | Sep 2011 | A1 |
20110255829 | Anderson et al. | Oct 2011 | A1 |
20120003877 | Bareel et al. | Jan 2012 | A1 |
20120021636 | Debendictis et al. | Jan 2012 | A1 |
20120133524 | Anderson et al. | May 2012 | A1 |
20120168521 | Jones et al. | Jul 2012 | A1 |
20120208401 | Petersen | Aug 2012 | A1 |
20120322310 | Taylor | Dec 2012 | A1 |
20130071084 | Nhep | Mar 2013 | A1 |
20140023328 | Lambourn | Jan 2014 | A1 |
20140219615 | Petersen et al. | Aug 2014 | A1 |
20140220794 | Taylor et al. | Aug 2014 | A1 |
20140241691 | Solheid et al. | Aug 2014 | A1 |
20140286610 | Anderson et al. | Sep 2014 | A1 |
Number | Date | Country |
---|---|---|
2499803 | Apr 2004 | CA |
101650457 | Feb 2010 | CN |
202600189 | Dec 2012 | 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 |
2004-165089 | Jun 2004 | JP |
WO 0065696 | Nov 2000 | 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 |
WO 2012149020 | Nov 2012 | WO |
WO 2014009344 | Jan 2014 | WO |
Entry |
---|
Avaya's Enhanced SYSTIMAX® iPatch System Enables IT Managers to Optimise Network Efficiency and Cut Downtime, Press Release, May 9, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030509 on Jan. 7, 2009. |
Avaya's Enhanced SYSTIMAX® iPatch System Enables IT Managers to Optimise Network Efficiency and Cut Downtime, Press Release, May 20, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030520 on Jan. 7, 2009. |
European Search Report for Application No. 14749636.8 dated Jul. 26, 2016. |
European Search Report for Application No. 14749636.8 dated Nov. 29, 2016. |
Extended European Search Report for Application No. 20173538.8 dated Sep. 24, 2020. |
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 for PCT/US2014/014870 dated May 19, 2014. |
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_gcil099991,00.html. |
Ohtsuki, F. et al., “Design of Optical Connectors with ID Modules,” Electronics and Communications in Japan, Part 1, vol. 77, No. 2, pp. 94-105 (Feb. 1994). |
SYSTIMAX® iPatch System Wins Platinum Network of the Year Award, Press Release, Jan. 30, 2003, obtained from http://www.avaya.com/usa/about-avaya/newsroom/news-releases/2003/pr-030130a on Jan. 7, 2009. |
TrueNet; TFP Series Rack Mount Fiber Panels, Spec Sheet; May 2008; 8 pages. |
Number | Date | Country | |
---|---|---|---|
20210033801 A1 | Feb 2021 | US |
Number | Date | Country | |
---|---|---|---|
61843718 | Jul 2013 | US | |
61761034 | Feb 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16388983 | Apr 2019 | US |
Child | 16995219 | US | |
Parent | 15722648 | Oct 2017 | US |
Child | 16388983 | US | |
Parent | 15065338 | Mar 2016 | US |
Child | 15722648 | US | |
Parent | 14169912 | Jan 2014 | US |
Child | 15065338 | US |