This disclosure relates to cable management systems/components and, more particularly, to cable management systems/components for use within IT devices.
In today's IT infrastructure, high availability is of paramount importance. Specifically, critical (and sometimes non-critical) components within an IT infrastructure are often layered in redundancy. For example, primary servers may be supported by backup servers; primary switches may be supported by backup switches; primary power supplies may be supported by backup power supplies; and primary storage systems may be supported by backup storage systems.
Oftentimes, various IT components that have different cabling requirements may be mounted within these IT racks, thus necessitating the use of different cabling, which may be difficult to change and may result in complications during the initial assembly of these IT components and/or the subsequent retrofit of the same.
In one implementation, a spring-pulley system is configured for use within an IT component and includes a cable assembly configured to electrically couple a fixed portion of an IT component to a slidable portion of the IT component. A pulley assembly is configured to engage the cable assembly. A spring assembly is configured to bias the pulley assembly toward a first position to absorb any slack in the cable assembly.
One or more of the following features may be included. A first end of the cable assembly may be coupled to the fixed portion of the IT component. A second end of the cable assembly may be coupled to the slidable portion of the IT component. The spring assembly may include at least one constant force spring. The at least one constant force spring may include at least one coil configured to be coupled to the pulley assembly. The cable assembly may be a portion of an internal cable bundle. The cable assembly may be configured to provide electrical power from the fixed portion of the IT component to the slidable portion of the IT component. The spring-pulley system may be coupled to the slidable portion of the IT component. The cable assembly may be configured to electrically couple at least a portion of a cabling module to at least a portion of an external cable termination module. The cabling module may be included within the slidable portion of the IT component. The external cable termination module may be included within the fixed portion of the IT component.
In another implementation, a spring-pulley system is configured for use within an IT component and includes a cable assembly configured to electrically couple a fixed portion of an IT component to a slidable portion of the IT component. A first end of the cable assembly is coupled to the fixed portion of the IT component and a second end of the cable assembly is coupled to the slidable portion of the IT component. A pulley assembly is configured to engage the cable assembly. A spring assembly is configured to bias the pulley assembly toward a first position to absorb any slack in the cable assembly.
One or more of the following features may be included. The spring assembly may include at least one constant force spring. The at least one constant force spring may include at least one coil configured to be coupled to the pulley assembly. The spring-pulley system may be coupled to the slidable portion of the IT component. The cable assembly may be configured to electrically couple at least a portion of a cabling module to at least a portion of an external cable termination module. The cabling module may be included within the slidable portion of the IT component. The external cable termination module may be included within the fixed portion of the IT component.
In another implementation, a spring-pulley system is configured for use within an IT component and includes a cable assembly configured to electrically couple a fixed portion of an IT component to a slidable portion of the IT component. The cable assembly is a portion of an internal cable bundle and is configured to provide electrical power from the fixed portion of the IT component to the slidable portion of the IT component. A pulley assembly is configured to engage the cable assembly. A spring assembly is configured to bias the pulley assembly toward a first position to absorb any slack in the cable assembly.
One or more of the following features may be included. A first end of the cable assembly may be coupled to the fixed portion of the IT component. A second end of the cable assembly may be coupled to the slidable portion of the IT component.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.
Like reference symbols in the various drawings indicate like elements.
Referring to
Examples of the various IT components (e.g., IT component 12) mountable within IT rack 10 may include but are not limited to: server systems, disk array systems, storage processor systems, storage processor/disk systems, and battery backup systems.
IT rack 10 may include frame 18 (which may include one or more vertical supports, horizontal supports, and cross braces) to which NEMA rails 14, 16 may be attached. NEMA rails 14, 16 may include a plurality of evenly spaced holes that may be configured for mounting the various IT components within IT rack 10. By standardizing the spacing between NEMA rails 14, 16, the various IT components that fit within a first IT rack may also fit within a second IT rack.
Typically, IT racks are defined in accordance with the number of rack units (U's) included within the rack. For example, a 1 U IT component is half as high as a 2 U IT component, which is half as high as a 4 U IT component. Accordingly, while the number of rack units available within a particular IT rack may be rigidly defined by the size of the IT rack, the number of IT components mountable within that IT rack may vary depending upon the size (in rack units) of the particular IT components being mounted within that IT rack. Therefore, by reducing the number of rack units that a particular IT component uses within an IT rack, additional IT computing devices may be mounted within the IT rack.
Referring to
Storage components may be the portion of rack-mountable computing device 50 that is configured to store data. Examples of such data may include but are not limited to data that is generated remotely (e.g., by applications that are executed on remote devices) or data that is generated locally (e.g., by applications that are executed on rack-mountable computing device 50). Accordingly, the storage component may be configured to include one or more storage devices, examples of which may include but are not limited to one or more rotating-media disk drives (e.g., SATA drives or SCSI drives) and/or one or more solid state storage devices (e.g., flash drives). For example and as shown in
The input/output components of rack-mountable computing device 50 may be the portion of rack-mountable computing device 50 that is configured to couple rack-mountable computing device 50 to a network infrastructure (e.g., network infrastructure 76), wherein network infrastructure 76 may be configured to couple rack-mountable computing device 50 to other rack-mountable computing devices, other IT components (e.g., server systems, disk array systems, storage processor systems, storage processor/disk systems, and battery backup systems), other networking devices (e.g., switches, routers, bridges, wireless access points), and/or end user computing devices (e.g., desktop computers, laptop computers, notebook computers, smartphones, tablet computers, etc.). Examples of network infrastructure 76 may include but are not limited to an Ethernet infrastructure; a fiber channel infrastructure; and an infiniband infrastructure.
The processing components of rack-mountable computing device 50 may be the portion of rack-mountable computing device 50 that is configured to process data, such as data that is generated remotely (e.g., by applications that are executed on remote devices) or data that is generated locally (e.g., by applications that are executed on rack-mountable computing device 50). Accordingly, the processing components of rack-mountable computing device 50 may be configured to include one or more microprocessors.
Referring also to
Referring also to
Additionally, slidable portion 104 of rack-mountable, hyper-converged computing device 100 may be configured so that the sub-components (e.g., storage devices, compute modules, memory modules) included within rack-mountable, hyper-converged computing device 100 may all be accessible and serviceable through the exposed top of slidable portion 104 once slidable portion 104 is slid forward and is clear of fixed portion 102 (as there will typically be another IT device mounted directly on top of rack-mountable, hyper-converged computing device 100).
Power supply units 106 within rack-mountable, hyper-converged computing device 100 may be coupled to slidable portion 104 of rack-mountable, hyper-converged computing device 100 and may, therefore, move with slidable portion 104 of rack-mountable, hyper-converged computing device 100. Accordingly, when rack-mountable, hyper-converged computing device 100 is in the extended/open position (as shown in
An upper portion (e.g., upper portion 114) of rear face 108 of rack-mountable, hyper-converged computing device 100 may be the area to which electrical power and data cables are attached. For example, data cables and power cables may be attached to various connectors on upper portion 114 of rear face 108 and interior cables carrying these signals may be routed within rack-mountable, hyper-converged computing device 100 in a manner that allows for this cabling to be coupled to and move with slidable portion 104 of rack-mountable, hyper-converged computing device 100.
Referring also to
As stated above, upper portion 114 of rear face 108 (which is affixed to fixed portion 102 of rack-mountable, hyper-converged computing device 100) may be configured so that electrical power and data cables may be attached to various connectors included therein/thereon. Accordingly and in this particular configuration, upper portion 114 of rear face 108 is shown to include plurality of host bus adapters 160 (for coupling data cables to rack-mountable, hyper-converged computing device 100). Internal data cables coupled to plurality of host bus adapters 160 may be routed within rack-mountable, hyper-converged computing device 100 and received by slidable portion 104 of rack-mountable, hyper-converged computing device 100 (which, as discussed above, may contain e.g., storage devices, computer modules, memory modules).
Upper portion 114 of rear face 108 is also shown to include external cable termination module 162 that (in this example) is configured to receive a plurality of discrete power sources. For example, as rack-mountable, hyper-converged computing device 100 is shown to include four discrete power supply units 150, 152, 154, 156, external cable termination module 162 may be configured to receive four discrete power sources (e.g., discrete power sources 164, 166, 168, 170), wherein discrete power sources 164, 166, 168, 170 may be releasably coupled to external cable termination module 162 and may be provided by one or more power distribution units (not shown). As is known in the art, a power distribution unit (or a main distribution unit) is a device fitted with multiple outputs that is designed to distribute electric power to e.g., racks of computers and networking equipment within a data center.
Accordingly, discrete power sources 164, 166, 168, 170 that are received by external cable termination module 162 may be routed within rack-mountable, hyper-converged computing device 100 and received by cabling module 158, wherein cabling module 158 may be configured to provide discrete power sources 164, 166, 168, 170 to discrete power supply units 150, 152, 154, 156 (respectively).
Referring also to
Cabling module 158 may include an input connector 202 configured to receive electrical power (e.g., discrete power sources 164, 166, 168, 170) from within rack-mountable, hyper-converged computing device 100. Cabling module 158 may include plurality of output connectors (e.g., output connectors 204, 206, 208, 210) configured to provide electrical power (e.g., discrete power sources 164, 166, 168, 170) to a plurality of subcomponents (e.g., discrete power supply units 150, 152, 154, 156) of rack-mountable, hyper-converged computing device 100. While in this particular example, output connectors 204, 206, 208, 210 are shown to provide discrete power sources 164, 166, 168, 170 (respectively) to discrete power supply units 150, 152, 154, 156 (respectively), this is for illustrative purposes only and in not intended to be a limitation of this disclosure, as other configurations are possible and are considered to be within the scope of this disclosure. Plurality of output connectors 204, 206, 208, 210 may include a plurality of electrical cords, wherein each of the plurality of electrical cords may include a plug (e.g., plug 212) configured to releasably engage one of plurality of power supply units (e.g., power supply unit 150).
Enclosure assembly 200 may be configured to be permanently affixed within rack-mountable, hyper-converged computing device 100 or releasably affixed within rack-mountable, hyper-converged computing device 100. For example and if permanently affixed, enclosure assembly 200 may be crimped to/spot-welded to rack-mountable, hyper-converged computing device 100. Alternatively and if releasably affixed, enclosure assembly 200 may be releasably affixed to rack-mountable, hyper-converged computing device 100 via one or more fasteners (e.g., that are received by threaded holes 214, 216, 218). In such a configuration, cabling module 158 may be configured to be a field replaceable unit.
Input connector 202 may be configured to releasably engage chassis connector 220 within rack-mountable, hyper-converged computing device 100. For example, chassis connector 220 may be rigidly affixed within rack-mountable, hyper-converged computing device 100 so that when cabling module 158 is slid into rack-mountable, hyper-converged computing device 100, chassis connector 220 may releasably engage input connector 202.
Through the use of cabling module 158, rack-mountable, hyper-converged computing device 100 may be quickly and easily reconfigured based upon power needs/requirements. For example and depending upon the needs of rack-mountable, hyper-converged computing device 100, discrete power supply units 150, 152, 154, 156 may have either IEC C13 connectors (which are rated for 120/240 VAC @ 15 amps) or IEC C19 connectors (which are rated for 120/240 VAC @ 20 amps). As each of these connectors has a different pin configuration, in the event that you need to upgrade your power supply units from IEC C13 to IEC C19, cabling module 158 (with IEC C13 connectors) may be simply removed and replaced with another cabling module 158 (with IEC C19 connectors).
Referring also to
As discussed above, data cables and power cables may be attached to various connectors on upper portion 114 of rear face 112 of rack-mountable, hyper-converged computing device 100 and the interior cables carrying these signals may be routed within rack-mountable, hyper-converged computing device 100 in a manner that allows for this cabling to be coupled to and move with slidable portion 104 of rack-mountable, hyper-converged computing device 100.
Accordingly and referring also to
Referring also to
Referring also to
Spring-pulley system 300 may include pulley assembly 302 that is biased toward the left (in this view) via spring assembly 304. Spring-pulley system 300 may include cable assembly 306 that may be physically and electrically coupled on first end 308 to fixed portion 102 of rack-mountable, hyper-converged computing device 100. Further, cable assembly 306 may include second end 310 that may be physically and electrically coupled to slidable portion 104 of rack-mountable, hyper-converged computing device 100.
In this particular embodiment, cable assembly 306 may be a portion of internal cable bundle 302. As discussed above, external cable termination module 162 may include one or more output connectors (e.g., output connectors 258, 260, 262, 264) configured to provide the electrical power to rack-mountable, hyper-converged computing device 100. Accordingly, each of output connectors 258, 260, 262, 264 may include at least a line voltage conductor and a neutral conductor, for a total of eight conductors. Therefore, internal cable bundle 302 (which may include at least eight conductors) may be split into two of cable assemblies 306 (each of which includes at least four conductors).
Continuing with the above-stated example and referring also to
As discussed above, pulley assembly 302 may be biased toward the left (in this view) via spring assembly 304. Accordingly, when pulley assembly 302 is drawn into position 318 due to the opening of rack-mountable, hyper-converged computing device 100, spring assembly 304 may continue to try to return pulley assembly 302 to position 312. Accordingly, when slidable portion 104 is moved from the opened position (as shown in
Referring also to
During use, the displacing of pulley assembly 302 from position 312 to position 318 (due to the opening of rack-mountable, hyper-converged computing device 100) may result in the uncoiling of coils 354, 356 of constant force springs 350, 352, wherein returning pulley assembly 302 from position 318 back to position 312 (due to the closing of rack-mountable, hyper-converged computing device 100) may result in the recoiling of coils 354, 356 of constant force springs 350, 352.
While spring assembly 304 is shown to include two constant force springs (e.g., constant force springs 350, 352), this is for illustrative purposes only and is not intended to be a limitation of this disclosure, as other configurations are possible and are considered to be within the scope of this disclosure. For example, the number of constant force springs may be increased or decreased depending upon design criteria and the amount of biasing needed.
General:
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
A number of implementations have been described. Having thus described the disclosure of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the disclosure defined in the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4579403 | Byrne | Apr 1986 | A |
5041002 | Byrne | Aug 1991 | A |
5987203 | Abel et al. | Nov 1999 | A |
6215654 | Wilkie et al. | Apr 2001 | B1 |
6407933 | Bolognia | Jun 2002 | B1 |
6646893 | Hardt | Nov 2003 | B1 |
6944383 | Herzog | Sep 2005 | B1 |
7140911 | Rector et al. | Nov 2006 | B1 |
7279634 | Chang | Oct 2007 | B1 |
7416435 | Onogi | Aug 2008 | B2 |
7491095 | Huang | Feb 2009 | B1 |
7873842 | Chen | Jan 2011 | B2 |
7994426 | Rizzuto | Aug 2011 | B1 |
8060682 | Genetti et al. | Nov 2011 | B1 |
8068351 | Figueroa et al. | Nov 2011 | B2 |
8144471 | Morimoto | Mar 2012 | B2 |
8241058 | Fisher | Aug 2012 | B1 |
8814445 | Gallegos | Aug 2014 | B2 |
8873250 | Kroupa | Oct 2014 | B2 |
8982582 | Malek et al. | Mar 2015 | B2 |
9104387 | Eichelberg | Aug 2015 | B1 |
9362635 | Wild et al. | Jun 2016 | B2 |
9392722 | Skirmont et al. | Jul 2016 | B2 |
9520043 | Alshinnawi et al. | Dec 2016 | B1 |
9531645 | Loiferman et al. | Dec 2016 | B2 |
9781859 | Wishman | Oct 2017 | B1 |
20020071266 | Ikeura | Jun 2002 | A1 |
20040041389 | Nishide et al. | Mar 2004 | A1 |
20050057912 | Hardt | Mar 2005 | A1 |
20050237724 | Fiorentino | Oct 2005 | A1 |
20060044754 | Hung | Mar 2006 | A1 |
20060262492 | Tsai | Nov 2006 | A1 |
20070270017 | Hardacker et al. | Nov 2007 | A1 |
20070270028 | Huang | Nov 2007 | A1 |
20080139022 | Chen et al. | Jun 2008 | A1 |
20100110628 | Barrenechea et al. | May 2010 | A1 |
20100172083 | Randall | Jul 2010 | A1 |
20100254652 | Kirkpatrick et al. | Oct 2010 | A1 |
20120044626 | Haigh | Feb 2012 | A1 |
20120044627 | Haigh | Feb 2012 | A1 |
20120069514 | Ross | Mar 2012 | A1 |
20120162959 | Terada | Jun 2012 | A1 |
20130198532 | Bailey et al. | Aug 2013 | A1 |
20130249286 | Hou et al. | Sep 2013 | A1 |
20130321997 | Yi | Dec 2013 | A1 |
20130342968 | Peterson et al. | Dec 2013 | A1 |
20140069680 | Alshinnawi et al. | Mar 2014 | A1 |
20140071602 | Alshinnawi et al. | Mar 2014 | A1 |
20140281614 | Mick et al. | Sep 2014 | A1 |
20140346866 | Feigl et al. | Nov 2014 | A1 |
20150060009 | Shelnutt et al. | Mar 2015 | A1 |
20150103488 | Tanaka | Apr 2015 | A1 |
20150116913 | Kwon et al. | Apr 2015 | A1 |
20150117077 | Huang et al. | Apr 2015 | A1 |
20150177808 | Sarti | Jun 2015 | A1 |
20150189787 | Bailey et al. | Jul 2015 | A1 |
20150208544 | Liao et al. | Jul 2015 | A1 |
20160044819 | Bailey et al. | Feb 2016 | A1 |
20160205804 | Hartman | Jul 2016 | A1 |
20160329689 | Yi | Nov 2016 | A1 |
20160369844 | Ito | Dec 2016 | A1 |
20170071073 | Chen et al. | Mar 2017 | A1 |
20170086325 | Connor et al. | Mar 2017 | A1 |
20170108899 | Thul | Apr 2017 | A1 |
20170111451 | Thul | Apr 2017 | A1 |
20170150635 | Huang et al. | May 2017 | A1 |
20170164505 | Sarti | Jun 2017 | A1 |
20170181314 | Leigh et al. | Jul 2017 | A1 |
20170222577 | Anderson | Aug 2017 | A1 |
20170303439 | Cader et al. | Oct 2017 | A1 |
Entry |
---|
Non-Final Office Action dated Oct. 20, 2017 in counterpart application U.S. Appl. No. 15/497,561. |
Non-Final Office Action dated Nov. 16, 2017 in counterpart U.S. Appl. No. 15/497,442. |
Final Office Action issued in U.S. Appl. No. 15/497,442, dated May 25, 2018. |