The present disclosure relates generally to information handling systems, and more particularly to a unibody construction triangular chassis.
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option is an information handling system. An information handling system generally processes, compiles, stores, or communicates information or data for business, personal, or other purposes. Technology and information handling needs and requirements can vary between different applications. Thus information handling systems can also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information can be processed, stored, or communicated. The variations in information handling systems allow information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems can include a variety of hardware and software resources that can be configured to process, store, and communicate information and can include one or more computer systems, graphics interface systems, data storage systems, networking systems, and mobile communication systems. Information handling systems can also implement various virtualized architectures. Data and voice communications among information handling systems may be via networks that are wired, wireless, or some combination. The chassis of an information handling system may provide a framework for housing the components of the information handling system.
It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings herein, in which:
The use of the same reference symbols in different drawings indicates similar or identical items.
The following description in combination with the Figures is provided to assist in understanding the teachings disclosed herein. The description is focused on specific implementations and embodiments of the teachings, and is provided to assist in describing the teachings. This focus should not be interpreted as a limitation on the scope or applicability of the teachings.
Base chassis 100 provides the support structure of the information handling system. Base chassis 100 is formed from gussets 110, 160, and 180, sides 120 and 140, and underside 170. Sides 120 and 140 are generally rectangular. Only an edge of gusset 160 and underside 170 is shown in
In many embodiments, gussets 110, 160, and 180, sides 120, 140, and 170, and other structural elements of base chassis 100 are fabricated from drawn sheet metal. Pressed sheet metal and other materials are contemplated as well. As shown in
In some embodiments, the rigidity provided by the construction of
Side 300 of
Gusset 400 of
Diagram 820 of
Diagram 830 of
At block 1020, the structural elements are assembled into the base chassis. The base chassis has a triangular profile with chamfered vertices. At block 1030, the assembling includes interlocking at least two of the structural elements. At block 1040, the assembling includes connecting two sides with each gusset, thereby forming a chamfered vertex at the gusset. In particular, the gussets may interlock with the sides.
At block 1050, a plastic chassis assembly is attached to the base chassis. The pieces of the plastic chassis assembly may resemble elements 710, 750, and 760 of
Other embodiments may include different shapes of structural elements for use in producing the chassis and different shapes of plastic pieces to produce a plastic chassis assembly. In many embodiments, fewer than three handles may be installed, and the pieces used to create the handles may differ from the pieces illustrated in
BIOS/EFI module 1140, disk controller 1150, and I/O interface 1170 are connected to chipset 1110 via an I/O channel 1112. An example of I/O channel 1112 includes a Peripheral Component Interconnect (PCI) interface, a PCI-Extended (PCI-X) interface, a high-speed PCI-Express (PCIe) interface, another industry standard or proprietary communication interface, or a combination thereof. Chipset 1110 can also include one or more other I/O interfaces, including an Industry Standard Architecture (ISA) interface, a Small Computer Serial Interface (SCSI) interface, an Inter-Integrated Circuit (I2C) interface, a System Packet Interface (SPI), a Universal Serial Bus (USB), another interface, or a combination thereof. BIOS/EFI module 1140 includes BIOS/EFI code operable to detect resources within information handling system 1100, to provide drivers for the resources, initialize the resources, and access the resources. BIOS/EFI module 1140 includes code that operates to detect resources within information handling system 1100, to provide drivers for the resources, to initialize the resources, and to access the resources.
Disk controller 1150 includes a disk interface 1152 that connects the disc controller to a hard disk drive (HDD) 1154, to an optical disk drive (ODD) 1156, and to disk emulator 1160. An example of disk interface 1152 includes an Integrated Drive Electronics (IDE) interface, an Advanced Technology Attachment (ATA) such as a parallel ATA (PATA) interface or a serial ATA (SATA) interface, a SCSI interface, a USB interface, a proprietary interface, or a combination thereof. Disk emulator 1160 permits a solid-state drive 1164 to be connected to information handling system 1100 via an external interface 1162. An example of external interface 1162 includes a USB interface, an IEEE 11194 (Firewire) interface, a proprietary interface, or a combination thereof. Alternatively, solid-state drive 1164 can be disposed within information handling system 1100.
I/O interface 1170 includes a peripheral interface 1172 that connects the I/O interface to an add-on resource 1174 and to network interface 1180. Peripheral interface 1172 can be the same type of interface as I/O channel 1112, or can be a different type of interface. As such, I/O interface 1170 extends the capacity of I/O channel 1112 when peripheral interface 1172 and the I/O channel are of the same type, and the I/O interface translates information from a format suitable to the I/O channel to a format suitable to the peripheral channel 1172 when they are of a different type. Add-on resource 1174 can include a data storage system, an additional graphics interface, a network interface card (NIC), a sound/video processing card, another add-on resource, or a combination thereof. Add-on resource 1174 can be on a main circuit board, on separate circuit board or add-in card disposed within information handling system 1100, a device that is external to the information handling system, or a combination thereof.
Network interface 1180 represents a NIC disposed within information handling system 1100, on a main circuit board of the information handling system, integrated onto another component such as chipset 1110, in another suitable location, or a combination thereof. Network interface device 1180 includes network channels 1182 and 1184 that provide interfaces to devices that are external to information handling system 1100. In a particular embodiment, network channels 1182 and 1184 are of a different type than peripheral channel 1172 and network interface 1180 translates information from a format suitable to the peripheral channel to a format suitable to external devices. An example of network channels 1182 and 1184 includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernet channels, proprietary channel architectures, or a combination thereof. Network channels 1182 and 1184 can be connected to external network resources (not illustrated). The network resource can include another information handling system, a data storage system, another network, a grid management system, another suitable resource, or a combination thereof.
While the computer-readable medium is shown to be a single medium, the term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” shall also include any medium that is capable of storing, encoding, or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein.
In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to store information received via carrier wave signals such as a signal communicated over a transmission medium. Furthermore, a computer readable medium can store information received from distributed network resources such as from a cloud-based environment. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is equivalent to a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
The information handling system can include memory (volatile (e.g. random-access memory, etc.), nonvolatile (read-only memory, flash memory etc.) or any combination thereof), one or more processing resources, such as a central processing unit (CPU), a graphics processing unit (GPU), hardware or software control logic, or any combination thereof. Additional components of the information handling system can include one or more storage devices, one or more communications ports for communicating with external devices, as well as, various input and output (I/O) devices, such as a keyboard, a mouse, a video/graphic display, or any combination thereof. The information handling system can also include one or more buses operable to transmit communications between the various hardware components. Portions of an information handling system may themselves be considered information handling systems.
When referred to as a “device,” a “module,” or the like, the embodiments described herein can be configured as hardware. For example, a portion of an information handling system device may be hardware such as, for example, an integrated circuit (such as an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a structured ASIC, or a device embedded on a larger chip), a card (such as a Peripheral Component Interface (PCI) card, a PCI-express card, a Personal Computer Memory Card International Association (PCMCIA) card, or other such expansion card), or a system (such as a motherboard, a system-on-a-chip (SoC), or a stand-alone device).
The device or module can include software, including firmware embedded at a device, such as a Pentium class or PowerPC™ brand processor, or other such device, or software capable of operating a relevant environment of the information handling system. The device or module can also include a combination of the foregoing examples of hardware or software. Note that an information handling system can include an integrated circuit or a board-level product having portions thereof that can also be any combination of hardware and software.
Devices, modules, resources, or programs that are in communication with one another need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices, modules, resources, or programs that are in communication with one another can communicate directly or indirectly through one or more intermediaries.
Although only a few exemplary embodiments have been described in detail herein, those skilled in the art will readily appreciate that many modifications are possible in the exemplary embodiments without materially departing from the novel teachings and advantages of the embodiments of the present disclosure. Accordingly, all such modifications are intended to be included within the scope of the embodiments of the present disclosure as defined in the following claims. In the claims, means-plus-function clauses are intended to cover the structures described herein as performing the recited function and not only structural equivalents, but also equivalent structures.
Number | Name | Date | Kind |
---|---|---|---|
D49524 | Andre | Aug 1916 | S |
3727979 | Schier | Apr 1973 | A |
D312423 | Orlinsky | Nov 1990 | S |
D317261 | Brown | Jun 1991 | S |
5345807 | Butts et al. | Sep 1994 | A |
5369549 | Kopp | Nov 1994 | A |
5434566 | Iwasa et al. | Jul 1995 | A |
5515040 | Lee et al. | May 1996 | A |
5574858 | Witte | Nov 1996 | A |
5790102 | Nassimi | Aug 1998 | A |
5909357 | Orr | Jun 1999 | A |
D418412 | Komatsu | Jan 2000 | S |
6098184 | Patterson, Jr. | Aug 2000 | A |
6107997 | Ure | Aug 2000 | A |
6135886 | Armstrong | Oct 2000 | A |
6157533 | Sallam | Dec 2000 | A |
6166723 | Schena et al. | Dec 2000 | A |
D471892 | Jordan | Mar 2003 | S |
6560095 | Zheng | May 2003 | B1 |
6587093 | Shaw et al. | Jul 2003 | B1 |
D480705 | Jordan | Oct 2003 | S |
D497163 | Andre | Oct 2004 | S |
D508491 | Choi | Aug 2005 | S |
7024625 | Shali | Apr 2006 | B2 |
D532780 | Proctor, Jr. | Nov 2006 | S |
7136045 | Rosenberg et al. | Nov 2006 | B2 |
7151672 | Campbell | Dec 2006 | B2 |
D543180 | Ra | May 2007 | S |
7710397 | Krah et al. | May 2010 | B2 |
7817135 | Shaw et al. | Oct 2010 | B2 |
D640227 | Wada | Jun 2011 | S |
8035616 | Shaw et al. | Oct 2011 | B2 |
8188842 | Otsuka | May 2012 | B2 |
8243018 | Farag et al. | Aug 2012 | B2 |
8405969 | Sullivan | Mar 2013 | B2 |
8553400 | Moran | Oct 2013 | B2 |
8577289 | Schlub et al. | Nov 2013 | B2 |
8662604 | Rajvanshi | Mar 2014 | B2 |
8894161 | Herreid, II | Nov 2014 | B2 |
D734478 | Labuschagne | Jul 2015 | S |
D737250 | Ingham | Aug 2015 | S |
20030112587 | Krause | Jun 2003 | A1 |
20060087805 | Massih | Apr 2006 | A1 |
20060183421 | Proctor, Jr. | Aug 2006 | A1 |
20060187011 | van der Meer | Aug 2006 | A1 |
20060262026 | Gainey | Nov 2006 | A1 |
20070072657 | Hyun | Mar 2007 | A1 |
20080007905 | Wilcox | Jan 2008 | A1 |
20090126450 | Su | May 2009 | A1 |
20090140985 | Liu | Jun 2009 | A1 |
20100127983 | Irani et al. | May 2010 | A1 |
20100148999 | Casparian et al. | Jun 2010 | A1 |
20100201626 | Krah et al. | Aug 2010 | A1 |
20100321301 | Casparian et al. | Dec 2010 | A1 |
20130122974 | Haramein | May 2013 | A1 |
20130279107 | Knopf | Oct 2013 | A1 |
20140247554 | Sharma | Sep 2014 | A1 |
20150197182 | Jones | Jul 2015 | A1 |
Number | Date | Country |
---|---|---|
WO 2012112275 | Aug 2012 | WO |
Entry |
---|
“Wieson's P-Sensor Efficiently Reduce the SAR from Handheld Device,” Wireless Application Business Unit, May 14, 2012, 2 pgs., http://www.wieson.com/go/en/wieson/news—show.php?nid=12392&catalog=Product%20News. |
“802.11n Demystified—Key considerations for n-abling the Wireless Enterprise,” Motorola White Paper, 802 11nDEM—WP—v4—0209, 12 pgs, Feb. 2009, http://www.motorolasolutions.com/web/Business/—Documents/White%20Paper/—Static%20files/802%2011nDEM—WP—v4—0209.pdf. |
Number | Date | Country | |
---|---|---|---|
20160034005 A1 | Feb 2016 | US |