This disclosure generally relates to information handling systems, and more particularly relates to controlled cable attenuation.
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.
Electrical cables (or simply cables) have become an integral part of many information handling systems such as, desktop computers, laptop computers, and servers. Cables may be used externally to connect multiple information handling systems together, or internally to connect various components together such as printed circuit boards (PCBs) within an information handling system. When one or more servers are installed within a rack, for example, communication between the servers can be easily accomplished through externally coupled cables. Internal cables are also commonly used within the servers for connecting Serial Attached Small Computer System Interface (SCSI), Serial Attached SCSI (SAS), Serial Advanced Technology Attachment (SATA) and non-volatile memory (NVME) backplanes.
Cables are commonly used in high-speed signal transmission applications, because they provide a low cable loss for signal propagation. However, with signal speeds steadily increasing, lowering the cable loss is becoming a major design challenge for future high-speed signal transmission applications. Even though cables provide a lower cable loss than other mediums, the loss through the cables may not be adequate to meet the channel budget specified in some high-speed data bus standards, such as the Peripheral Component Interconnect Express (PCIe) standard, at certain cable lengths (e.g., cable lengths greater than 700 mm). While ultra-loss materials are currently being considered, there is an ever present need to design cables with lower cable loss.
A cable comprising a conductor in a center of the cable, a dielectric layer surrounding the conductor and a resistive coating may be provided. The resistive coating may be applied to an exposed portion of the conductor and disposed with the dielectric layer. The resistance of the resistive coating when combined with an impedance of the cable prior to application of the resistive coating reaches a target impedance.
It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the Figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements. Embodiments incorporating teachings of the present disclosure are shown and described with respect to the drawings presented 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 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.
A coaxial cable (or simple “coax”) is one type of electrical cable commonly used for high-speed signal transmission. As known in the art, a coaxial cable typically includes a center conductor, an insulating dielectric layer surrounding the center conductor, and an outer conductor surrounding the insulating dielectric layer, all of which is surrounded by a protective outer jacket. In a coaxial cable, the center conductor is used for single-ended signal transmission, while the outer conductor (or shield) is connected to ground.
In cable 100 or in particular, conductor 110 may be used for signal transmission. When an alternating current (AC) signal is applied to conductor 110, the alternating current is distributed within the conductor. Conductor 110 may be cylindrical in shape and be formed from one of any electrically conductive material. For example, conductor 110 may be implemented or formed from silver, copper, tin-plated copper, silver-plated copper, or the like. However, conductor 110 is not restricted to such materials, and may be implemented with any suitable electrically conductive material.
Dielectric layer 105 may include one of any substantially electrically insulative material. For example, dielectric layer 105 may be implemented with polyethylene or polytetrafluoroethylene. However, dielectric layer 105 is not restricted to such materials, and may be implemented with any suitable insulating material having low conductivity.
In connecting various components inside and outside an information handling system, various lengths of cables may be used. For example, typical cable length in servers can vary from approximately 150 millimeter (mm) to 750 mm or longer. As such, a configuration design of how the various components are connected in a server may need to support both a 150 mm length cable and a 750 mm length cable. However, this is difficult because the length of the cable can affect the signal attenuation. For example, shorter cables typically do not dampen reflections and crosstalk and thus encounter more failures.
Currently, system design is optimized for a midrange cable length. This means that there are varying ranges of cable loss, also referred to as cable attenuation, in the system as depicted in
The greater the length of a cable, the greater the attenuation or cable loss. In this example, longer cables typically have greater cable loss than the shorter cables. As loss of the longer cable cannot be reduced, the present disclosure provides a system and method to increase the loss of the shorter cable to mirror the loss of the longer cable. This can be accomplished by applying additional coating that can be adjusted based on a desired or target loss for that particular cable.
Here, resistive coating, such as resistive coating 115 may be applied to an exposed portion of the conductor of a shorter cable so that its resistance is increased until a target resistance is reached. The measure of the resistance value may be controlled by the thickness, type, and length of resistive coating 115. Resistive coating 115 may also be applied more than once, such that thickness 125 is increased to reach the desired resistance. The target resistance may be the resistance of the longest cable used in the system design. In an example, resistive coating 115, or resistive layer, may be a conductive paint, which in turn may enable control over how the resistive coating is applied. For example, resistive coating 115 may be applied to a certain length120 and certain thickness 125, such as by applying more than one coat of the conductive paint. Here, assuming that cable 100 is of a shorter length than the cable length that the configuration design is optimized for, resistive coating 115 of length 120 and thickness 125 may be applied to an exposed portion of conductor 110. In an example, the application of resistive coating 115 may cause cable 100 to perform substantially similar to a longer cable, such that the cable becomes more lossy and reflections and crosstalk are dampened.
Resistive coating 115 may be applied on a portion of the surface of conductor 110 providing additional resistance to cable 100. Resistive coating 115 may be applied to a particular length and a particular thickness, such as length 120 and thickness 125 respectively. Resistive coating 115 may include a conductive pigment such as graphite, silver, copper, nickel, or carbon. The pigment may be dissolved or suspended as particles in a solution. Each of these pigments has different resistivity properties. For example, graphite may have higher electrical resistivity than nickel or copper. Thus, in addition to the length and thickness of the resistive coating, the type of conductive paint to be used may be chosen based on the target resistance.
The target resistance, also referred to as target impedance, may be calculated as Z0=RResistive-coat∥Zcable, wherein Z0 is the target resistance, RResistive-coat is the resistance of resistive coating 115 and Zcable is the cable impedance of cable 100 prior to the application of resistive coating 115. The cable impedance includes the impedance of both conductor 110 and dielectric layer 105. Given two resistances and/or impedances in parallel, the effective resulting impedance is the average of the two resistances and/or impedances. Given a known target resistance Z0 and cable impedance Zcable, a RResistive-coat may be calculated as the delta between the target resistance and the cable impedance. In one example, if the target resistance is one hundred ohms and the cable impedance is eighty ohms, then the resistance of the resistive coating is one hundred and twenty ohms. In addition, given the target impedance, a target cable loss may be determined such as based on one or more models.
In addition, although it is shown in
Referring to
Graph 300 shows a frequency 305 in gigahertz (GHz) along the x-axis and the cable loss in decibels (dB) along the y-axis. Line 320 represents cable loss for a cable 1 with a length of 100 mm, wherein the cable loss is 0.667 dB at a frequency of 1.6e+10. Line 325 represents cable loss for a cable 2 with a length of 300 mm, wherein the cable loss is −2 dB at the frequency of 1.6e+10. Line 330 represents cable loss for a cable 3 with a length of 500 mm, wherein the cable loss is −3.33 dB at the frequency of 1.6e+10. Line 335 represents cable loss for a cable 4 with a length of 700 mm, wherein the cable loss is −4.67 dB at the frequency of 1.6e+10. It should be noted that apart from length the cables 1-4 are substantially similar. Thus, the range of cable loss at frequency of 1.6e+10 is [0.667, 4.67].
Graph 400 shows a frequency 305 in GHz along the x-axis and the cable loss in dB along the y-axis. Line 420 represents cable loss for a cable 1 with a length of 100 mm, wherein the cable loss is −4.59 dB at a frequency of 1.6e+10. Line 325 represents cable loss for a cable 2 with a length of 300 mm, wherein the cable loss is −4.59 dB at the frequency of 1.6e+10. Line 330 represents cable loss for cable 3 with a length of 500 mm, wherein the cable loss is −4.59 dB at the frequency of 1.6e+10. Line 335 represents cable loss for cable 4 with a length of 700 mm, wherein the cable loss is −4.59 dB at the frequency of 1.6e+10. It should be noted that apart from length and the amount of resistive coating, cables 1-4 are substantially similar. The cable loss at frequency of 1.6e+10 of cables 1-4 is the same at −4.59 dB.
The method proceeds to decision block 525, where it is determined whether the target impedance is reached. For example, the cable may be tested to determine whether the cable with the resistive layer reached the target impedance, such as by measuring high frequency loss. If the target impedance is reached, then the “YES” branch is taken and the method ends. If the target impedance is not reached, then the “NO” branch is taken and the method proceeds to block 530, where an adjustment to the resistive coating is made. For example, portions of the resistive coating may be blasted away or laser trimmed to reduce the resistance until the target impedance is reached. In another example, the thickness and/or the length of the resistive coating may be increased such as by applying another coat of the conductive paint. In yet another example, another resistive coating may be applied to the other end of the cable.
Information handling system 600 can 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 system 600 includes a processors 602 and 604, an input/output (I/O) interface 610, memories 620 and 625, a graphics interface 630, a basic input and output system/universal extensible firmware interface (BIOS/UEFI) module 640, a disk controller 650, a hard disk drive (HDD) 654, an optical disk drive (ODD) 656, a disk emulator 660 connected to an external solid state drive (SSD) 664, an I/O bridge 670, one or more add-on resources 674, a trusted platform module (TPM) 676, a network interface 680, a management device 690, and a power supply 695. Processors 602 and 604, I/O interface 610, memories 620 and 625, graphics interface 630, BIOS/UEFI module 640, disk controller 650, HDD 654, ODD 656, disk emulator 660, SSD 664, I/O bridge 670, add-on resources 674, TPM 676, and network interface 680 operate together to provide a host environment of information handling system 600 that 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 600.
In the host environment, processor 602 is connected to I/O interface 610 via processor interface 606, and processor 604 is connected to the I/O interface via processor interface 608. Memory 620 is connected to processor 602 via a memory interface 622. Memory 625 is connected to processor 604 via a memory interface 627. Graphics interface 630 is connected to I/O interface 610 via a graphics interface 632, and provides a video display output 635 to a video display 634. In a particular embodiment, information handling system 600 includes separate memories that are dedicated to each of processors 602 and 604 via separate memory interfaces. An example of memories 620 and 625 include 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.
BIOS/UEFI module 640, disk controller 650, and I/O bridge 670 are connected to I/O interface 610 via an I/O channel 612. An example of I/O channel 612 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. I/O interface 610 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/UEFI module 640 includes BIOS/UEFI code operable to detect resources within information handling system 600, to provide drivers for the resources, initialize the resources, and access the resources. BIOS/UEFI module 640 includes code that operates to detect resources within information handling system 600, to provide drivers for the resources, to initialize the resources, and to access the resources.
Disk controller 650 includes a disk interface 652 that connects the disk controller to HDD 654, to ODD 656, and to disk emulator 660. An example of disk interface 652 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 660 permits SSD 664 to be connected to information handling system 300 via an external interface 662. An example of external interface 662 includes a USB interface, an IEEE 1394 (Firewire) interface, a proprietary interface, or a combination thereof. Alternatively, solid-state drive 664 can be disposed within information handling system 600.
I/O bridge 670 includes a peripheral interface 672 that connects the I/O bridge to add-on resource 674, to TPM 676, and to network interface 680. Peripheral interface 672 can be the same type of interface as I/O channel 612, or can be a different type of interface. As such, I/O bridge 670 extends the capacity of I/O channel 612 when peripheral interface 672 and 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 channel 672 when they are of a different type. Add-on resource 674 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 674 can be on a main circuit board, on separate circuit board or add-in card disposed within information handling system 600, a device that is external to the information handling system, or a combination thereof.
Network interface 680 represents a NIC disposed within information handling system 600, on a main circuit board of the information handling system, integrated onto another component such as I/O interface 610, in another suitable location, or a combination thereof. Network interface device 680 includes network channels 682 and 684 that provide interfaces to devices that are external to information handling system 600. In a particular embodiment, network channels 682 and 684 are of a different type than peripheral channel 672 and network interface 680 translates information from a format suitable to the peripheral channel to a format suitable to external devices. An example of network channels 682 and 684 includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernet channels, proprietary channel architectures, or a combination thereof. Network channels 682 and 684 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.
Management device 690 represents 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 600. In particular, management device 690 is 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 (I2C) interface, a PCIe interface, or the like, to provide an out-of-band (00B) 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 600, such as system cooling fans and power supplies. Management device 690 can 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 600, to receive BIOS/UEFI or system firmware updates, or to perform other task for managing and controlling the operation of information handling system 600. Management device 690 can 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 system 600 when the information handling system is otherwise shut down. An example of management device 690 include 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 device 690 may 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.