Patent ID: 12241478

DETAILED DESCRIPTION

In the following description, details are set forth by way of example to facilitate discussion of the disclosed subject matter. It should be apparent to a person of ordinary skill in the field, however, that the disclosed embodiments are examples and not exhaustive of all possible embodiments.

As used herein, a reference numeral refers to a class or type of entity, and any letter following such reference numeral refers to a specific instance of a particular entity of that class or type. Thus, for example, a hypothetical entity referenced by ‘12A’ may refer to a particular instance of a particular class/type, and the reference ‘12’ may refer to a collection of instances belonging to that particular class/type or any one instance of that class/type in general.

An information handling system (IHS) may include a hardware resource or an aggregate of hardware resources operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, and/or utilize various forms of information, intelligence, or data for business, scientific, control, entertainment, or other purposes, according to one or more embodiments. For example, an IHS may be a personal computer, a desktop computer system, a laptop computer system, a server computer system, a mobile device, a tablet computing device, a personal digital assistant (PDA), a consumer electronic device, an electronic music player, an electronic camera, an electronic video player, a wireless access point, a network storage device, or another suitable device and may vary in size, shape, performance, functionality, and price. In one or more embodiments, a portable IHS may include or have a form factor of that of or similar to one or more of a laptop, a notebook, a telephone, a tablet, and a PDA, among others. For example, a portable IHS may be readily carried and/or transported by a user (e.g., a person). In one or more embodiments, components of an IHS may 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, and a video display, among others. In one or more embodiments, IHS may include one or more buses operable to transmit communication between or among two or more hardware components. In one example, a bus of an IHS may include one or more of a memory bus, a peripheral bus, and a local bus, among others. In another example, a bus of an IHS may include one or more of a Micro Channel Architecture (MCA) bus, an Industry Standard Architecture (ISA) bus, an Enhanced ISA (EISA) bus, a Peripheral Component Interconnect (PCI) bus, HyperTransport (HT) bus, an inter-integrated circuit (I2C) bus, a serial peripheral interface (SPI) bus, a low pin count (LPC) bus, an enhanced serial peripheral interface (eSPI) bus, a universal serial bus (USB), a system management bus (SMBus), and a Video Electronics Standards Association (VESA) local bus, among others.

In one or more embodiments, an IHS may include firmware that controls and/or communicates with one or more hard drives, network circuitry, one or more memory devices, one or more I/O devices, and/or one or more other peripheral devices. For example, firmware may include software embedded in an IHS component utilized to perform tasks. In one or more embodiments, firmware may be stored in non-volatile memory, such as storage that does not lose stored data upon loss of power. In one example, firmware associated with an IHS component may be stored in non-volatile memory that is accessible to one or more IHS components. In another example, firmware associated with an IHS component may be stored in non-volatile memory that may be dedicated to and includes part of that component. For instance, an embedded controller may include firmware that may be stored via non-volatile memory that may be dedicated to and includes part of the embedded controller.

An IHS may include a processor, a volatile memory medium, non-volatile memory media, an I/O subsystem, and a network interface. Volatile memory medium, non-volatile memory media, I/O subsystem, and network interface may be communicatively coupled to processor. In one or more embodiments, one or more of volatile memory medium, non-volatile memory media, I/O subsystem, and network interface may be communicatively coupled to processor via one or more buses, one or more switches, and/or one or more root complexes, among others. In one example, one or more of a volatile memory medium, non-volatile memory media, an I/O subsystem, and a network interface may be communicatively coupled to the processor via one or more PCI-Express (PCIe) root complexes. In another example, one or more of an I/O subsystem and a network interface may be communicatively coupled to processor via one or more PCIe switches.

In one or more embodiments, the term “memory medium” may mean a “storage device”, a “memory”, a “memory device”, a “tangible computer readable storage medium”, and/or a “computer-readable medium”. For example, computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive, a floppy disk, etc.), a sequential access storage device (e.g., a tape disk drive), a compact disk (CD), a CD-ROM, a digital versatile disc (DVD), a random access memory (RAM), a read-only memory (ROM), a one-time programmable (OTP) memory, an electrically erasable programmable read-only memory (EEPROM), and/or a flash memory, a solid state drive (SSD), or any combination of the foregoing, among others.

In one or more embodiments, one or more protocols may be utilized in transferring data to and/or from a memory medium. For example, the one or more protocols may include one or more of small computer system interface (SCSI), Serial Attached SCSI (SAS) or another transport that operates with the SCSI protocol, advanced technology attachment (ATA), serial ATA (SATA), a USB interface, an Institute of Electrical and Electronics Engineers (IEEE) 1394 interface, a Thunderbolt interface, an advanced technology attachment packet interface (ATAPI), serial storage architecture (SSA), integrated drive electronics (IDE), or any combination thereof, among others.

A volatile memory medium may include volatile storage such as, for example, RAM, DRAM (dynamic RAM), EDO RAM (extended data out RAM), SRAM (static RAM), etc. One or more of non-volatile memory media may include nonvolatile storage such as, for example, a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM, NVRAM (non-volatile RAM), ferroelectric RAM (FRAM), a magnetic medium (e.g., a hard drive, a floppy disk, a magnetic tape, etc.), optical storage (e.g., a CD, a DVD, a BLU-RAY disc, etc.), flash memory, a SSD, etc. In one or more embodiments, a memory medium can include one or more volatile storages and/or one or more nonvolatile storages.

In one or more embodiments, a network interface may be utilized in communicating with one or more networks and/or one or more other information handling systems. In one example, network interface may enable an IHS to communicate via a network utilizing a suitable transmission protocol and/or standard. In a second example, a network interface may be coupled to a wired network. In a third example, a network interface may be coupled to an optical network. In another example, a network interface may be coupled to a wireless network. In one instance, the wireless network may include a cellular telephone network. In a second instance, the wireless network may include a satellite telephone network. In another instance, the wireless network may include a wireless Ethernet network (e.g., a Wi-Fi network, an IEEE 802.11 network, etc.).

In one or more embodiments, a network interface may be communicatively coupled via a network to a network storage resource. For example, the network may be implemented as, or may be a part of, a storage area network (SAN), personal area network (PAN), local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a wireless local area network (WLAN), a virtual private network (VPN), an intranet, an Internet or another appropriate architecture or system that facilitates the communication of signals, data and/or messages (generally referred to as data). For instance, the network may transmit data utilizing a desired storage and/or communication protocol, including one or more of Fibre Channel, Frame Relay, Asynchronous Transfer Mode (ATM), Internet protocol (IP), other packet-based protocol, Internet SCSI (iSCSI), or any combination thereof, among others.

In one or more embodiments, a processor may execute processor instructions in implementing at least a portion of one or more systems, at least a portion of one or more flowcharts, at least a portion of one or more methods, and/or at least a portion of one or more processes. In one example, a processor may execute processor instructions from one or more memory media in implementing at least a portion of one or more systems, at least a portion of one or more flowcharts, at least a portion of one or more methods, and/or at least a portion of one or more processes. In another example, a processor may execute processor instructions via a network interface in implementing at least a portion of one or more systems, at least a portion of one or more flowcharts, at least a portion of one or more methods, and/or at least a portion of one or more processes.

In one or more embodiments, a processor may include one or more of a system, a device, and an apparatus operable to interpret and/or execute program instructions and/or process data, among others, and may include one or more of a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), and another digital or analog circuitry configured to interpret and/or execute program instructions and/or process data, among others. In one example, a processor may interpret and/or execute program instructions and/or process data stored locally (e.g., via memory media and/or another component of an IHS). In another example, a processor may interpret and/or execute program instructions and/or process data stored remotely (e.g., via a network storage resource).

In one or more embodiments, an I/O subsystem may represent a variety of communication interfaces, graphics interfaces, video interfaces, user input interfaces, and/or peripheral interfaces, among others. For example, an I/O subsystem may include one or more of a touch panel and a display adapter, among others. For instance, a touch panel may include circuitry that enables touch functionality in conjunction with a display that is driven by a display adapter.

A non-volatile memory medium may include an operating system (OS) and applications (APPs). In one or more embodiments, one or more of an OS and APPs may include processor instructions executable by a processor. In one example, a processor may execute processor instructions of one or more of OS and APPs via a non-volatile memory medium. In another example, one or more portions of the processor instructions of one or more of an OS and APPs may be transferred to a volatile memory medium and a processor may execute the one or more portions of the processor instructions.

Non-volatile memory medium may include information handling system firmware (IHSFW). In one or more embodiments, IHSFW may include processor instructions executable by a processor. For example, IHSFW may include one or more structures and/or one or more functionalities of and/or compliant with one or more of a basic input/output system (BIOS), an Extensible Firmware Interface (EFI), a Unified Extensible Firmware Interface (UEFI), and an Advanced Configuration and Power Interface (ACPI), among others. In one instance, a processor may execute processor instructions of IHSFW via non-volatile memory medium. In another instance, one or more portions of the processor instructions of IHSFW may be transferred to volatile memory medium, and processor may execute the one or more portions of the processor instructions of IHSFW via volatile memory medium.

Common Portable Chassis Designs have a Bottom Cover with a Vent

Referring toFIG.1, a portable chassis100containing an information handling system typically comprises bottom cover104coupled to two or more side covers106. For cooling an information handling system in chassis100, fan housing108comprises first wall108aand one or more side walls108b, wherein first wall108may support fan hub110and the one or more side walls108bmay protect a plurality of fan blades112. Airflow116may enter fan housing108through fan inlet opening114.

As used herein, the terms “bottom” and “side” or “sides” may refer to a common orientation of a portable chassis, wherein a portable chassis (e.g., a laptop)100with a plurality of covers is generally oriented such that a cover associated with chassis100sitting on surface118is referred to as a bottom cover and other covers may be referred to as side covers or a top cover.

A force applied to bottom cover104may cause bottom cover104to deflect, particularly if the material used to form bottom cover104is a resilient material (e.g., plastic). To prevent damage to fan blades112, fan blades112may be recessed in fan housing108, and fan housing108may comprise fan shroud120extending radially inward of side walls108band in contact with bottom cover104. Fan shroud120may contact bottom cover104to prevent a force applied on bottom cover104from deflecting bottom cover104into contact with fan blades112.

Bottom cover104may be formed with vent122, which may prevent debris from entering fan inlet opening114and may further limit how much bottom cover104may be deflected before contact with fan blades112. As depicted inFIG.1, fan blades112may have a uniform blade width profile such that a fan blade width is constant over the fan blade length (e.g., the fan blade width at an innermost radius near fan hub110may equal the fan blade width at an outermost radius of the fan blade112.

No-Vent Chassis for Concave Fans

Referring toFIG.2, chassis200for containing an information handling system in a mobile device may comprise bottom cover204and a plurality of side covers206, in which one or more side covers206may have one or more chassis air inlets202and bottom cover204may be formed with a continuous surface (e.g., without vent122as depicted inFIG.1). Fan housing208may comprise first wall208aand one or more side walls208b, wherein first wall108may support fan hub110and the one or more side walls108bmay protect a plurality of fan blades212. Airflow216may enter fan housing208through fan inlet opening214.

Fan hub110and fan blades212may form part of a concave fan, wherein fan blades212may have a fan blade length to define a fan diameter but have a non-uniform blade width. For example, fan blades212depicted inFIG.2may have a fan blade width that increases radially outward of fan hub110.

To improve airflow in a concave fan, fan housing208may be configured with fan shroud220that is angled (e.g., non-parallel) relative to first wall208abased on the fan blade width. Advantageously, chassis200such as depicted inFIG.2with fan shroud220that is angled relative to first wall208acan dramatically reduce the high air flow impedance between fan blades212and bottom cover204, allowing some relatively lower power cooling systems to not have a large bottom vent (e.g., without vent122as depicted inFIG.1) without sacrificing the cooling performance. Chassis200without a bottom vent may provide a premium style for a mobile device (e.g., a laptop) and may also reduce or eliminate intake vent blocking problems when the mobile device is positioned or oriented on certain surfaces118(e.g., on a user's lap).

Turning toFIG.3, although a concave fan can provide a significant thermal benefit, the need for airflow via one or more chassis air inlets202results in a mechanical challenge for bottom covers204formed from more resilient materials (e.g., plastics), particularly for a mechanical deflection test (also called a pogo test) in the area near fan inlet214. For a laptop chassis with traditional bottom fan inlet and a non-concave fan (e.g., chassis100inFIG.1), a typical solution may be to add embosses to fan shroud120, strengthening fan shroud120and therefore reducing its deformation under the load. However, in a no-bottom-vent design, air flow216must go through the narrow channel between fan housing208and bottom cover204. Adding embosses on fan housing308will block air flow216.

Embodiments disclosed herein may include a fan housing with a plurality of tabs located proximate a fan inlet opening. The tabs may extend in a direction substantially parallel with an axis of rotation of fan blades such that deflection of the bottom cover contacts the tabs instead of the fan blades. In some embodiments, the plurality of tabs may contact a bottom cover.

Embodiments may include a support structure on a fan housing comprising a plurality of tabs at the edge of the fan inlet opening and may further include a ring or disc that is connected to the tabs within the fan inlet opening. Advantageously, a mechanical support located proximate a fan inlet opening may significantly reduce the support distance and therefore greatly increase the amount of force that can be tolerated before the bottom cover touches a fan hub or fan blades.

Tabs Extend to Protect Fan Blades from a Deflection of a Chassis Bottom Cover

Turning toFIG.4, embodiments of a cooling system for a portable chassis may comprise fan housing400for supporting fan hub110and a plurality of fan blades212. Fan housing400may be formed with first wall408afor supporting fan hub110and a plurality of fan blades212, one or more side walls408coupled to first wall408a, and fan shroud420coupled to side walls408b. Fan hub110rotates fan blades212to draw airflow216into fan housing400through fan inlet214and airflow216exits fan housing400through exit416.

Fan shroud420may be formed as a generally smooth surface (e.g., no embosses) to minimize negative effects on airflow216. Fan shroud420may be formed with fan inlet214positioned near fan hub110to allow airflow216into fan housing400. Fan shroud420may further comprise a plurality of tabs410positioned proximate fan inlet214. Tabs410may extend a height (HTAB) in a direction substantially parallel with an axis of rotation (R) associated with fan hub110, wherein the height ensures any deflection of bottom cover204contacts tabs410before contacting fan hub110or fan blades212. Each tab410may have a width (WTAB) to minimize any negative effect of positioning tabs410in airflow216.

Disc Coupled to Tabs Further Protects Fan Blades from a Deflection of a Chassis Bottom Cover

Turning toFIG.5, embodiments of a cooling system for a portable chassis may comprise fan housing500for supporting fan hub110and a plurality of fan blades212. Fan housing500may be formed with first wall508afor supporting fan hub110and a plurality of fan blades212, one or more side walls508bcoupled to first wall508a, and fan shroud520coupled to side walls508b. Fan hub110rotates fan blades212to draw airflow216into fan housing500through fan inlet214and airflow216exits fan housing500through exit416.

Fan shroud520may be formed as a generally smooth surface (e.g., no embosses) to minimize negative effects on airflow216. Fan shroud520may be formed with fan inlet214positioned near fan hub110to allow airflow216into fan housing500. Fan shroud520may further comprise a plurality of tabs510positioned proximate fan inlet214. Tabs510may extend a height (HTAB) in a direction substantially parallel with an axis of rotation (R) associated with fan hub110, wherein the height ensures any deflection of bottom cover204contacts tabs510before contacting fan hub110or fan blades212. Each tab510may have a width (WTAB) to minimize any negative effect of positioning tabs510in airflow216.

In some embodiments, fan housing500comprises disc502coupled to tabs510, wherein disc502may have a disc diameter less than a diameter of fan inlet214. In some embodiments, disc502may have a disc diameter that is less than an outer diameter of fan hub110. In some embodiments, tabs510may be configured such that a force applied to disc502causes a deflection of tabs510to cause disc502to contact fan hub110. Disc502coupled to tabs510may limit how much bottom cover204can be deflected since disc502may contact fan hub110.

A Ring Coupled to Tabs Further Protects Fan Blades from a Larger Deflection of a Chassis Bottom Cover

Turning toFIG.6, embodiments of a cooling system for a portable chassis may comprise fan housing600for supporting fan hub110and a plurality of fan blades212. Fan housing600may be formed with first wall608afor supporting fan hub110and a plurality of fan blades212, one or more side walls608bcoupled to first wall608a, and fan shroud620coupled to side walls608b. Fan hub110rotates fan blades212to draw airflow216into fan housing600through fan inlet214and airflow216exits fan housing500through exit416.

Fan shroud620may be formed as a generally smooth surface (e.g., no embosses) to minimize negative effects on airflow216. Fan shroud620may be formed with fan inlet214positioned near fan hub110to allow airflow216into fan housing600. Fan shroud620may further comprise a plurality of tabs610positioned proximate fan inlet214. Tabs610may extend a height (HTAB) in a direction substantially parallel with an axis of rotation (R) associated with fan hub110, wherein the height ensures any deflection of bottom cover204contacts tabs610before contacting fan hub110or fan blades212. Each tab610may have a width (WTAB) to minimize any negative effect of positioning tabs610in airflow216.

In some embodiments, fan housing600may comprise ring602coupled to tabs610, wherein ring602has an outer diameter and an inner diameter. In some embodiments, tabs610may be configured from a resilient material such that a force applied to bottom cover204causes bottom cover204to contact ring602. In some embodiments, the inner diameter of ring602may be configured such that, if a force is applied to bottom cover204to deflect tabs610, ring602may be positioned around fan hub110(e.g., fan hub110may start to pass through ring602). Thus, embodiments of fan housing600may allow for greater deflection of bottom cover204than embodiments of fan housing500.

All Designs Improve Over Existing Approaches

Embodiments may greatly increase the structural support to protect fan blades212from contact with bottom cover20. Referring to Chart1, finite element analysis (FEA) simulations indicate all embodiments described above exceed a pogo test requirement of withstanding at least 10 Kg of force applied to bottom cover204.

CHART 1MAXIMUMPOGO FORCECONFIG-ALLOWEDURATIONDESCRIPTION(KG)1NO EMBOSSES AND NO SUPPORT5.7STRUCTURE (FIG. 2)2NO EMBOSSES, TABS ON FAN14.5SHROUD (FIG. 4)3NO EMBOSSES, TABS ON FAN11.2SHROUD + DISC (FIG. 5)4NO EMBOSSES, TABS ON FAN16.1SHROUD + RING (FIG. 6)

As indicated by the results in Chart1, a fan assembly configured with no supports (e.g., fan housing200depicted inFIG.2) may tolerate only about 5.7 Kg of force before bottom cover204contacts fan hub110or fan blades212. However, embodiments described herein may be configured to tolerate at least 10 Kg of force. For example, configuration3may tolerate approximately 11.2 Kg of force before disc502contacts fan fub210, configuration2may tolerate approximately 14.5 Kg of force before fan shroud420contacts fan blades212and configuration4may tolerate approximately 16.1 Kg of force before fan shroud620contacts fan blades212.

Referring to Chart2, finite element analysis (FEA) for an embodiment similar to the embodiment depicted inFIG.6was compared against actual test results for a fan assembly without support (e.g., fan assembly200inFIG.2). For materials, bottom cover204was defined with a modulus of 12 GPa, fan housing408was defined as 0.4 mm thick steel, the fan housing side walls were defined as PC/ABS plastic with a modulus of 2 GPa and the fan base is steel. For the test, a pogo rod of 10 mm diameter was used to deflect a bottom cover204a maximum of 1.3 mm (until bottom cover204was within 1.0 mm of fan hub110).

CHART 2FEA-BASEDMAXIMUMTESTACCEPTABLERESULTSCONFIG-POGOIN AURATIONDESCRIPTIONFORCE (KG)CHASSIS (KG)1Concave fan without2.42.0 to 2.5any support structure2Concave fan with tabs8.49.0 to 10.5(e.g., FIG. 4)

The FEA simulation results matched reasonably well with actual measured data for the embodiment depicted inFIG.4. Accordingly, the FEA results for other embodiments are expected to be similarly accurate.

The above disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments which fall within the true spirit and scope of the present disclosure. Thus, to the maximum extent allowed by law, the scope of the present disclosure is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description.