A typical data center may include multiple equipment modules housed in racks. Equipment modules might include servers, disk arrays, routers, and others. In some situations, a user such as a system administrator or technician may want to connect to a particular equipment module at the physical location of the equipment module within the data center. For example, the user may wish to connect to the equipment to provide management instructions or receive diagnostic information from the equipment.
Certain examples are described in the following detailed description and in reference to the drawings, in which:
The techniques disclosed herein describe a technique for enabling wireless communication in a computing device, such as a rack-mounted computing device. In the examples described herein, a computing device is filled with an antenna that enables wireless communication with a component of the computing device. The antenna is included in a latch assembly, which is also used to couple the computing device to a rack, sometimes also referred to as a chassis. The latch can be made of plastic or any other suitable dielectric material that will not interfere with the antenna. The addition of the antenna to the computing device involves changes to a part of the computing device that can be easily and inexpensively replaced. In this way, the addition of wireless capability can be implemented with few design changes, and existing units can be easily upgraded at reduced cost.
The computing device 102 includes a pair of latch assemblies 104. The latch assemblies 104 are configured to mechanically couple the computing device 102 to the rack 100. In the example shown in
One or both latch assemblies 104 may include an antenna 108 that enables wireless communication with a component of the computing device 102. In some examples, the antenna 108 may be a Near-Field Communications (NFC) antenna. However, other types of antennas and communication protocols can be used, including Radio Frequency Identification (RFD), Wifi, bluetooth, and others.
The face 110 of the computing device 102 is the surface that will generally be exposed and accessible when the computing device 102 is installed in the rack 100. Often there is little space on the face 110 of computing device 102 for additional features. By including the antenna 108 in the latch assembly 104, which is disposed on the side of the computing device 102 adjacent to the face 110, the antenna 108 can be included without taking up any space on the front of the computing device 102. Furthermore, when the latch assembly 104 is coupled to the rack 100, the face of the latch assembly 104 is located outside of the metal enclosure of the rack 100. Thus, placing the antenna 108 in the latch assembly 104 may prevent the rack 100 from interfering with proper operation of the antenna 108.
The antenna 108 may enable one-way or two-way communications between a component of the computing device 102 and a user's mobile device, such as a laptop computer, tablet computer, or smartphone. In this way, the user can receive information from the computing device and can send data or commands to the computing device. The information received from the computing device 102 can include diagnostic information, configuration information, identification information, and the like. Data or commands sent to the computing device 102 can include configuration commands, information requests, firmware or software updates, and the like.
In some examples, the computing device 102 is a server with a management controller that provides out-of-band management, and the antenna 108 is electrically coupled to the management controller. Out-of-band management is a computer management technique that enables the user to control the computing device 102 remotely. In out-of-band management, management instructions are received through a communication channel that bypasses the computing device's main processors. Out-of-band management enables an administrator to remotely turn on a computer, update a computer's Basic Input/Output System (BIOS), and monitor computer resources even while a computer's main processor is powered down. An out-of-band management controller is sometimes referred to as a baseboard management controller (BMC) or Integrated Lights-Out (iLO) management controller. One example of the latch assembly 104 is described further below in relation
In the example shown in
The antenna 108 is electrically coupled to a component of the rack-mounted computing device 102 through the cable 204, which may terminate at a connector 206. The cable 204 can include any suitable number of conductors, which may depend, at least in part, on the communication protocol used. The cable 204 is routed from the antenna 108 through the latch body 202, emerging from the back the latch body 202 and running along the length of the computing device 102 to the appropriate component, such as a management controller.
The latch 200 may be coupled to the latch body (not shown) by a pin 306 that enables the latch 200 to pivot. When assembled, the pin 306 passes through the hole 308, which is located at the pivot point of the latch 200. The back of the latch 200 includes an opening 310 that enables the cable 204 to extend from the antenna 108 out of the latch 200 and into the latch body 202. The opening 310 may be positioned near the pivot point to reduce the movement of the cable 204 during the actuation of the latch 200.
It will be appreciated that the latch 200 is just one latch 200 that can be implemented in accordance with the present techniques and that other configurations are also possible. For example, the lever 200 may be formed around the antenna 108, such as by injection molding.
The rear of the latch assembly 104 can also include one or more bolt holes 404, some or all of which may be disposed inside of posts 406. The bolt holes 404 may serve different purposes depending on the design considerations of a particular implementation. One or more bolt holes 404 may be used to couple the latch assembly 104 to the computing device 102. One or more bolt holes 404 may also be used to couple the latch assembly to the rack 100. The number and placement of the bolt holes may vary from what is shown in
The cable 204 can be routed through the latch body 202 in any suitable manner. In the example shown in
The example latch assembly 104 also includes an attachable cable cap 500. The cable cap 500 can be attached to the latch body 202 after the cable 204 has been installed. The cable cap 500 helps to hold the cable in place and protects the cable 204 from damage. The cable cap 500 can be formed to fit the contour of the corresponding mating surfaces of the latch body 202, such as the bolt hole posts 406. The cable cap 500 also proves a gap that the cable 204 can pass through, enabling the cable 204 to exit from the back side of the latch assembly 104. The cable cap 500 can also include one or more tabs 502 by which the cable cap 500 can snap into place.
At block 602, electronic components are disposed within an enclosure. The electronic components are configured in accordance with the design of a particular computing device. The computing device may be any suitable type of computing device, including a server, a storage array, a processing node, a networking device such as a router or a switch, and any combination thereof, among others. The enclosure is configured to be disposed within a rack and may include one or more mechanical or electrical components that are configured to facilitate being disposed in a rack. For example, the enclosure may include mechanical features that facilitate inserting and securing the enclosure to the rack. The enclosure may also include electrical contacts that mate with electrical contacts of the rack and enable components within the enclosure to be communicatively coupled to other components through a backplane of the rack.
At block 604, an antenna is disposed within a latch assembly. The antenna may be any suitable type of antenna including an NFC antenna, a Radio Frequency Identification (RFID) tag, Wifi, Bluetooth, and others. The antenna may be disposed inside the latch portion of the latch assembly, in other words, the portion of the latch assembly configured to be manually actuated by the user. The latch may be formed of any suitable dielectric that will reduce interference with the antenna, including various types of plastics. The latch may be a molded plastic part that includes a space for disposing an antenna, as shown in
At block 606, the latch assembly is mechanically coupled to the enclosure of the computing device. As shown in
In some examples, the addition of the latch assembly to the enclosure of the computing device occurs in the course of upgrading the computing device. The computing device may already include one or more standard latch assemblies, i.e., latch assemblies without an antenna. At least one of the standard latches may be removed and replaced with the latch assembly described herein. In this way, existing equipment can be upgraded to add wireless management capability with very few changes to the computing device.
The process flow diagram of
The present examples may be susceptible to various modifications and alternative forms and have been shown only for illustrative purposes. Furthermore, it is to be understood that the present techniques are not intended to be limited to the particular examples disclosed herein. Indeed, the scope of the appended claims is deemed to include all alternatives, modifications, and equivalents that are apparent to persons skilled in the art to which the disclosed subject matter pertains.
Filing Document | Filing Date | Country | Kind |
---|---|---|---|
PCT/US2015/012009 | 1/20/2015 | WO | 00 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2016/118112 | 7/28/2016 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6133884 | Talvitie | Oct 2000 | A |
6567274 | Tusan | May 2003 | B1 |
6994192 | Chang | Feb 2006 | B1 |
7265968 | Champion | Sep 2007 | B2 |
8816857 | Nordin | Aug 2014 | B2 |
8854822 | Hazzard | Oct 2014 | B2 |
9214749 | Li | Dec 2015 | B2 |
9554480 | Freeman | Jan 2017 | B2 |
20020022460 | Lintern | Feb 2002 | A1 |
20050285801 | Reece et al. | Dec 2005 | A1 |
20060089108 | Lagnado et al. | Apr 2006 | A1 |
20060142048 | Aldridge et al. | Jun 2006 | A1 |
20060273962 | Brench | Dec 2006 | A1 |
20070240463 | Antonucci | Oct 2007 | A1 |
20080137284 | Flynn | Jun 2008 | A1 |
20080244052 | Bradicich | Oct 2008 | A1 |
20090108995 | Tucker | Apr 2009 | A1 |
20100277866 | Chen | Nov 2010 | A1 |
20110012709 | Payson | Jan 2011 | A1 |
20110202172 | Hayashi | Aug 2011 | A1 |
20120026646 | Thielmann et al. | Feb 2012 | A1 |
20120161938 | Kilian | Jun 2012 | A1 |
20120218076 | Zacchio | Aug 2012 | A1 |
20130135811 | Dunwoody | May 2013 | A1 |
20140254086 | Li et al. | Sep 2014 | A1 |
20140292496 | Tredoux | Oct 2014 | A1 |
20140318198 | Gokcebay | Oct 2014 | A1 |
20150228138 | Simmonds | Aug 2015 | A1 |
Number | Date | Country |
---|---|---|
102044848 | May 2011 | CN |
103988091 | Aug 2014 | CN |
102006034000 | Jan 2008 | DE |
2012238253 | Dec 2012 | JP |
Entry |
---|
Extended European Search Report, EP Application No. 15879148.7, dated Mar. 13, 2018, pp. 1-7, EPO. |
International search Report and Written Opinion received for PCT Application No. PCT/US2015/012009, dated Oct. 20, 2015, 9 pages. |
Number | Date | Country | |
---|---|---|---|
20170367212 A1 | Dec 2017 | US |