A liquid cooling system includes first and second coolant tubes and a coupler to couple the first coolant tube to the second coolant tube. The first coolant tube receives coolant liquid from a first element of the liquid cooling system. The second coolant tube provides the coolant liquid to a second element of the liquid cooling system. The coupler is configured to receive an electrical signal to constrict a flow of the coolant liquid.
Legal claims defining the scope of protection, as filed with the USPTO.
a first coolant tube to receive coolant liquid from a first element of the liquid cooling system, wherein the coolant liquid includes ferromagnetic particles; a second coolant tube to provide the coolant liquid to a second element of the liquid cooling system; and a coupler to couple the first coolant tube to the second coolant tube; wherein the coupler is configured to receive an electrical signal to constrict a flow of the coolant liquid. . A liquid cooling system, comprising:
claim 1 . The liquid cooling system of, wherein the coupler includes a wire winding around a perimeter of the coupler, the wire winding to receive the electrical signal.
claim 2 . The liquid cooling system of, wherein, when the coupler receives the electrical signal, the wire winding creates a magnetic field within the coupler.
(canceled)
claim 3 . The liquid cooling system of, wherein, when the coupler receives the electrical signal, the magnetic field within the coupler creates a floating obstruction of the ferromagnetic particles.
claim 5 . The liquid cooling system of, wherein, when the electrical signal has a first value, the floating obstruction partially obstructs a flow of the coolant liquid.
claim 6 . The liquid cooling system of, wherein the floating obstruction reduces a leak in the liquid cooling system.
claim 6 . The liquid cooling system of, wherein, when the electrical signal has a second value greater than the first value, the floating obstruction fully obstructs the flow.
claim 1 . The liquid cooling system of, wherein the electrical signal is received in response to a detection of a coolant liquid leak.
claim 9 . The liquid cooling system of, wherein the leak is at the coupler.
providing, in a liquid cooling system, a first coolant tube to receive coolant liquid from a first element of the liquid cooling system, wherein the coolant liquid includes ferromagnetic particles; providing, in the liquid cooling system, a second coolant tube to provide the coolant liquid to a second element of liquid cooling system; providing, in the liquid cooling system, a coupler to couple the first coolant tube to the second coolant tube; and receiving, by the coupler, an electrical signal to constrict a flow of the coolant liquid. . A method, comprising:
claim 11 providing, in the coupler, a wire winding around a perimeter of the coupler; and receiving, by the wire winding, the electrical signal. . The method of, further comprising:
claim 12 . The method of, wherein, when the coupler receives the electrical signal, the wire winding creates a magnetic field within the coupler.
(canceled)
claim 13 . The method of, wherein, when the coupler receives the electrical signal, the magnetic field within the coupler creates a floating obstruction of the ferromagnetic particles.
claim 15 . The method of, wherein, when the electrical signal has a first value, the floating obstruction partially obstructs a flow of the coolant liquid.
claim 16 . The method of, wherein the floating obstruction reduces a leak in the liquid cooling system.
claim 16 . The method of, wherein, when the electrical signal has a second value greater than the first value, the floating obstruction fully obstructs the flow.
claim 11 . The method of, wherein the electrical signal is received in response to a detection of a coolant liquid leak.
a first coolant tube to receive coolant liquid from a first element of the liquid cooling system, wherein the coolant liquid includes ferromagnetic particles; a second coolant tube to provide the coolant liquid to a second element of the liquid cooling system; a coupler to couple the first coolant tube to the second coolant tube; and a leak detector configured to provide an electrical signal in response to a leak of the coolant liquid; wherein the coupler is configured to receive the electrical signal and to create a floating obstruction of the ferromagnetic particles within the coupler to constrict a flow of the coolant liquid. . A liquid cooling system, comprising:
Complete technical specification and implementation details from the patent document.
This disclosure relates to information handling systems, and more particularly relates to electrically controlling a venturi to stop leaks in a direct liquid cooling (DLC) system in an information handling system.
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, and/or communicates information or data for business, personal, or other purposes. Because technology and information handling needs and requirements may vary between different applications, information handling systems may 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 may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software resources that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
A liquid cooling system may include first and second coolant tubes and a coupler to couple the first coolant tube to the second coolant tube. The first coolant tube may receive coolant liquid from a first element of the liquid cooling system. The second coolant tube may provide the coolant liquid to a second element of the liquid cooling system. The coupler may be configured to receive an electrical signal to constrict a flow of the coolant liquid
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 following discussion will focus on specific implementations and embodiments of the teachings. This focus is provided to assist in describing the teachings, and should not be interpreted as a limitation on the scope or applicability of the teachings. However, other teachings can certainly be used in this application. The teachings can also be used in other applications, and with several different types of architectures, such as distributed computing architectures, client/server architectures, or middleware server architectures and associated resources.
1 FIG. 100 100 100 110 120 130 130 130 a d a d a d illustrates a direct liquid cooling (DLC) system. DLC systemprovides cooling for critical components within information handling systems, for example in a data center or other high-density computing environment. DLC systemincludes a chiller, a headerand a number of information handling systems-. Each one of information handling systems-include one or more components that generate large amounts of heat in the enclosure of their respective information handling systems. For example, information handling systems-may include one or more processors (CPUs), chipset components, graphics processing units (GPUs), memory devices, storage devices, or the like, that represent a large portion of the thermal load of the respective information handling systems.
100 130 132 110 120 120 132 132 132 120 110 100 a d a d a d a d a d In order to remove the heat generated in an information handling system, manufacturers and users are turning to DLC systems like DLC systemto more efficiently and effectively manage the heat generated within their information handling systems and data centers. In this regard, information handling systems-each include one or more cold plate-to remove the heat from the high-heat generating components. As such, chilleroperates to supply chilled coolant liquid (as illustrated by the dotted lines) to header. Headerincludes a cold manifold that distributes the chilled coolant liquid to each of cold plates-. Cold plates-are configured to be thermally connected to the high-heat generating components, where the heat from the components is thermally transferred to the coolant liquid. The heated coolant liquid (indicated by the doted/dashed lines) is returned from cold plates-to headerwhere a cold manifold combines the heated coolant liquid for return to chiller. In this regard, DLC systemis a closed-loop system, rechilling the coolant liquid for redistribution throughout the DLC system.
100 110 120 132 140 100 130 140 a d a d DLC systemis characterized by the need to connect the components together to move the coolant liquid throughout the DLC system. In particular, each component (e.g., chiller, header, and cold plates-includes couplersthat couple the respective component to tubing that spans the distance between the respective components. DLC systems similar to DLC systemare prone to develop liquid coolant leaks. This presents a particular hazard when a leak develops within the enclosure of information handling systems-, where sensitive electronic components can be damaged, for example, when the liquid coolant bridges electrical circuits creating short circuits. Various mechanisms for mitigating liquid coolant leaks may include the application of highly absorbent material on the printed circuit boards (PCBs) of the information handling system, leak detection mechanisms such as leak detection ropes and the like, and the consequent shutting down of the information handling system when a liquid coolant leak is detected. It has been understood by the inventors of the current disclosure that couplers such as couplersare more prone to develop liquid coolant leaks than are the components and tubing that are connected by the couplers.
2 FIG. 200 200 210 212 222 140 200 220 220 220 222 220 222 224 226 222 226 224 222 226 illustrates a portion of an exemplary information handling systemwhich includes a DLC system to provide cooling for one or more component of the information handling system. Information handling systemincludes coolant tubesandthat are coupled together by a couplersimilar to coupler, as described above. Information handling systemfurther includes a liquid coolant leak detection and mitigation system(hereinafter “detection system”). Detection systemoperates to detect a coolant leak and to electrically mitigate the coolant leak via coupler. As such, detection systemincludes coupler, a leak detector, and a controller. Coupleroperates to receive an electrical signal from controllerthat engages the coupler to minimize or stop the coolant leak, as described further below. Leak detectoroperates to detect a coolant leak from couplerand to provide an electrical signal to controllerindicating that the coupler is leaking.
224 222 220 222 224 222 226 224 222 In a particular embodiment, leak detectoris localized to couplersuch that a coolant leak that is detected by the leak detector is highly likely to be from the coupler. In this case, detection systemoperates to control only couplerto minimize or stop the coolant leak. That is, leak detectoris a single-point leak detector that is situated to detect single-point coolant leaks from coupler, and controlleroperates on a one-to-one correlation between the leak detector and the coupler. In other embodiments, leak detectorprovides a wider coverage of more than one coupler similar to coupler, and the detection of a coolant leak results in the minimization or stoppage of the coolant leak by engaging multiple couplers, as needed or desired. The methods and mechanisms for detecting a coolant leak in an information handling system are known in the art and will not be further described herein, except as may be needed to illustrate the current embodiments.
3 3 FIGS.A andB 3 3 FIGS.A andB 300 310 320 325 310 320 325 330 320 325 330 310 320 325 310 320 325 320 325 310 illustrate a portion of a DLC systemincluding a couplerthat couples coolant tubesandtogether.more particularly illustrate a cross section of couplerand coolant tubesand. A coolant liquidflows in the illustrated direction from coolant tubeto coolant tube. Coolant liquidflows with a particular velocity which, for the purposes of the current disclosure, will be described as being a low velocity flow, or alternatively that coolant velocity is slow. Coupleris shown as having a slip-fitting to coolant tubesand, such as where the coolant tubes are glued, doped, or otherwise sealed to the coupler. However, other coupling mechanisms are herein contemplated, such as threaded fittings, compression couplings, or other types of coupling mechanisms as needed or desired. Further, it will be understood that couplerand coolant tubesandmay typically have a circular cross section, but this is not necessary, and other cross sectional configurations, such as square cross sections, rectangular cross sections, ovoid cross sections, or other cross sectional configurations may be utilized, as needed or desired. Further, coolant tubesandare illustrated as having a common size, but this is not necessary, and the coolant tubes may have differing sizes and couplermay be configured to adapt the relative sizes of the coolant tubes, as needed or desired.
310 315 315 310 330 335 315 335 330 3 FIG.A 3 FIG.A Couplerincludes a wire windingaround the perimeter of the coupler that is connected to a positive electrical contact (Vdc+) and a negative electrical contact (Vdc−). Here, it will be understood that a current applied to wire windingwill result in the creation of a strong magnetic field on the inside of coupler. In a particular embodiment, coolant liquidincludes ferromagnetic particlesthat flow with the coolant liquid, as illustrated inby the even distribution of the ferromagnetic particles. Thuswill be understood to represent a condition where no current is being provided to wire winding, and ferromagnetic particlesmove freely with the flow of coolant liquid.
3 FIG.B 300 310 325 220 315 310 335 330 315 335 330 335 315 illustrates a case where DLC system, and particularly couplerhas developed a coolant leak on the coolant tubeside. In this case, a detection system similar to detection system, as described above, may operate to detect the coolant leak, and to apply a current to wire winding, creating a strong magnetic field inside of coupler. Ferromagnetic particlesare held within the magnetic field to form a constriction in the flow of coolant liquid. Such a constriction is known to cause a venturi effect at the narrowing of the flow, resulting in an increase in the coolant velocity in the region of the constriction. In keeping with the venturi effect, the increase in the coolant velocity is accompanied by an associated reduction in pressure at the site of the leak, thereby slowing the leak. It will be understood that, if a high enough current is applied to wire winding, the induced magnetic field will be strong enough to retain ferromagnetic particlesto completely block the flow of coolant liquid, as needed or desired. Ferromagnetic particlesmay include magnetizable metallic particles, carboxyl (chromium dioxide) particles, or the like, and may be wholly formed of the associated ferromagnetic material, or may be formed as a coating on an underlying structure, such as a polystyrene particle, or the like. Note that the electrical contacts to wire windingare illustrated as being direct current (DC) contacts (i.e., Vdc+ and Vdc−), but this is not necessarily so, and an alternating current (AC) signal or another type of electrical signal may be provided as needed or desired.
4 FIG. 400 400 400 400 400 400 400 illustrates a generalized embodiment of an information handling systemsimilar to information handling system. For purpose of this disclosure an information handling system can include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, information handling systemcan be a personal computer, a laptop computer, a smart phone, a tablet device or other consumer electronic device, a network server, a network storage device, a switch router or other network communication device, or any other suitable device and may vary in size, shape, performance, functionality, and price. Further, information handling systemcan include processing resources for executing machine-executable code, such as a central processing unit (CPU), a programmable logic array (PLA), an embedded device such as a System-on-a-Chip (SoC), or other control logic hardware. Information handling systemcan also include one or more computer-readable medium for storing machine-executable code, such as software or data. Additional components of information handling systemcan include one or more storage devices that can store machine-executable code, one or more communications ports for communicating with external devices, and various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. Information handling systemcan also include one or more buses operable to transmit information between the various hardware components.
400 400 402 404 410 420 425 430 440 450 454 456 460 462 470 474 476 480 490 495 402 404 410 420 430 440 450 454 456 460 462 470 474 476 480 400 400 Information handling systemcan include devices or modules that embody one or more of the devices or modules described below, and operates to perform one or more of the methods described below. Information handling systemincludes a processorsand, an input/output (I/O) interface, memoriesand, a graphics interface, a basic input and output system/universal extensible firmware interface (BIOS/UEFI) module, a disk controller, a hard disk drive (HDD), an optical disk drive (ODD), a disk emulatorconnected to an external solid state drive (SSD), an I/O bridge, one or more add-on resources, a trusted platform module (TPM), a network interface, a management device, and a power supply. Processorsand, I/O interface, memory, graphics interface, BIOS/UEFI module, disk controller, HDD, ODD, disk emulator, SSD, I/O bridge, add-on resources, TPM, and network interfaceoperate together to provide a host environment of information handling systemthat operates to provide the data processing functionality of the information handling system. The host environment operates to execute machine-executable code, including platform BIOS/UEFI code, device firmware, operating system code, applications, programs, and the like, to perform the data processing tasks associated with information handling system.
402 410 406 404 408 In the host environment, processoris connected to I/O interfacevia processor interface, and processoris connected to the I/O interface via processor interface.
420 402 422 425 404 427 430 410 432 436 434 400 402 404 420 430 Memoryis connected to processorvia a memory interface. Memoryis connected to processorvia a memory interface. Graphics interfaceis connected to I/O interfacevia a graphics interface, and provides a video display outputto a video display. In a particular embodiment, information handling systemincludes separate memories that are dedicated to each of processorsandvia separate memory interfaces. An example of memoriesandinclude random access memory (RAM) such as static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NV-RAM), or the like, read only memory (ROM), another type of memory, or a combination thereof.
440 450 470 410 412 412 410 440 400 440 400 2 BIOS/UEFI module, disk controller, and I/O bridgeare connected to I/O interfacevia an I/O channel. An example of I/O channelincludes 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. I/O interfacecan 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 (IC) interface, a System Packet Interface (SPI), a Universal Serial Bus (USB), another interface, or a combination thereof. BIOS/UEFI moduleincludes BIOS/UEFI code operable to detect resources within information handling system, to provide drivers for the resources, initialize the resources, and access the resources. BIOS/UEFI moduleincludes code that operates to detect resources within information handling system, to provide drivers for the resources, to initialize the resources, and to access the resources.
450 452 454 456 460 452 460 464 400 462 462 464 400 Disk controllerincludes a disk interfacethat connects the disk controller to HDD, to ODD, and to disk emulator. An example of disk interfaceincludes 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 emulatorpermits SSDto be connected to information handling systemvia an external interface. An example of external interfaceincludes a USB interface, an IEEE 1394 (Firewire) interface, a proprietary interface, or a combination thereof. Alternatively, solid-state drivecan be disposed within information handling system.
470 472 474 476 480 472 412 470 412 472 472 474 474 400 I/O bridgeincludes a peripheral interfacethat connects the I/O bridge to add-on resource, to TPM, and to network interface. Peripheral interfacecan be the same type of interface as I/O channel, or can be a different type of interface. As such, I/O bridgeextends the capacity of I/O channelwhere peripheral interfaceand the I/O channel are of the same type, and the I/O bridge translates information from a format suitable to the I/O channel to a format suitable to the peripheral channelwhere they are of a different type. Add-on resourcecan 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 resourcecan be on a main circuit board, on separate circuit board or add-in card disposed within information handling system, a device that is external to the information handling system, or a combination thereof.
480 400 410 480 482 484 400 482 484 472 480 482 484 482 484 Network interfacerepresents a NIC disposed within information handling system, on a main circuit board of the information handling system, integrated onto another component such as I/O interface, in another suitable location, or a combination thereof. Network interface deviceincludes network channelsandthat provide interfaces to devices that are external to information handling system. In a particular embodiment, network channelsandare of a different type than peripheral channeland network interfacetranslates information from a format suitable to the peripheral channel to a format suitable to external devices. An example of network channelsandincludes InfiniBand channels, Fibre Channel channels, Gigabit Ethernet channels, proprietary channel architectures, or a combination thereof. Network channelsandcan 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.
490 400 490 400 490 400 400 490 400 490 490 2 Management devicerepresents one or more processing devices, such as a dedicated baseboard management controller (BMC) System-on-a-Chip (SoC) device, one or more associated memory devices, one or more network interface devices, a complex programmable logic device (CPLD), and the like, that operate together to provide the management environment for information handling system. In particular, management deviceis connected to various components of the host environment via various internal communication interfaces, such as a Low Pin Count (LPC) interface, an Inter-Integrated-Circuit (IC) interface, a PCIe interface, or the like, to provide an out-of-band (OOB) mechanism to retrieve information related to the operation of the host environment, to provide BIOS/UEFI or system firmware updates, to manage non-processing components of information handling system, such as system cooling fans and power supplies. Management devicecan include a network connection to an external management system, and the management device can communicate with the management system to report status information for information handling system, to receive BIOS/UEFI or system firmware updates, or to perform other task for managing and controlling the operation of information handling system. Management devicecan operate off of a separate power plane from the components of the host environment so that the management device receives power to manage information handling systemwhere the information handling system is otherwise shut down. An example of management deviceinclude a commercially available BMC product or other device that operates in accordance with an Intelligent Platform Management Initiative (IPMI) specification, a Web Services Management (WSMan) interface, a Redfish Application Programming Interface (API), another Distributed Management Task Force (DMTF), or other management standard, and can include an Integrated Dell Remote Access Controller (iDRAC), an Embedded Controller (EC), or the like. Management devicemay further include associated memory devices, logic devices, security devices, or the like, as needed or desired.
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.
The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover any and all such modifications, enhancements, and other embodiments that fall within the scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention 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.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
August 29, 2024
March 5, 2026
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.