M.2 WLAN module holder

Abstract

A device holder for holding an M.2 device to a printed circuit board is provided. The device holder includes a support portion, a cover portion, and a strap configured to hold the support portion to the cover portion. The seating portion is configured to be affixed to the printed circuit board and provide a seating on which a first end of the M.2 device can be seated. The cover portion is configured to allow a second end of the M.2 device to be inserted into the M.2 connector in an open position and to retain the M.2 device to the mount portion in a closed position.

Description

Technical Field

[0001] The present disclosure generally relates to information handling systems, and more particularly to an M.2 WLAN module cage for an information handling system. Background Art

[0002] As the value and use of information continue to grow, 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 commercial, personal, or other purposes. Because technology and information handling needs and requirements may vary between different applications, information handling systems may also vary in terms of what information is processed, how the information is processed, how much information is processed, stored, or communicated, and how quickly and efficiently the information can be processed, stored, or communicated. Variations in information handling systems allow an information handling system to be general-purpose or configured for a particular user or particular use (such as financial transaction processing, reservations, enterprise data storage, or global communications). Additionally, an information handling system may include a variety of hardware and software resources that can be configured to process, store, and communicate information, and may include one or more computer systems, data storage systems, and networking systems. Summary of the Invention

[0003] A device cage for holding an M.2 device to a printed circuit board may be provided. The device cage may include a support portion, a cover portion, and a strap configured to hold the support portion to the cover portion. The support portion may be configured to attach to the printed circuit board and provide a support for a first end of the M.2 device on which the M.2 device can be seated. The cover portion may be configured to allow a second end of the M.2 device to be inserted into an M.2 connector in an open position and to hold the M.2 device to the support portion in a closed position. Brief Description of the Drawings

[0004] It should be understood that, for simplicity and clarity of illustration, the elements shown in the drawings are not necessarily drawn to scale. For example, the dimensions of some elements are exaggerated relative to other elements. Embodiments incorporating the teachings of the present disclosure are shown and described with reference to the drawings presented herein, in which:

[0005] FIGS. 1A and 1B are perspective views of an M.2 device mounting assembly that may be known in the art;

[0006] Figure 2 is a perspective view of an M.2 device mounting assembly according to an embodiment of the present disclosure;

[0007] Figure 3A and Figure 3B is a perspective view of an M.2 device cage according to an embodiment of the present disclosure;

[0008] Figures 4A to 4G is a view showing a method for mounting an M.2 device for assembly Figure 2 ;

[0009] Figure 5 is a side view of an M.2 device mounting assembly according to another embodiment of the present disclosure; and

[0010] Figure 6 is a block diagram showing a general information handling system according to another embodiment of the present disclosure.

[0011] The use of the same reference numerals in different figures indicates like or identical items. DETAILED DESCRIPTION

[0012] The following description is provided in conjunction with the accompanying figures to assist in understanding the teachings disclosed herein. The following discussion will focus on specific embodiments and implementations of the teachings. Providing such focus aids in describing the teachings and should not be construed as limiting the scope or applicability of the teachings. However, other teachings may certainly be used in this application. The present teachings may 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.

[0013] FIG. 1A shows an M.2 device mounting assembly 100 that may be known in the art. Assembly 100 represents a mounting arrangement for mounting an M.2 device within an information handling system. An M.2 device represents an integrated device that complies with one or more standards and specifications defined by the PCI Special Interest Group (PCISIG). Specifically, assembly 100 represents a mounting arrangement for mounting an M.2 wireless local area network (WLAN) card 120 onto a printed circuit board (PCB) 110. Thus, arrangement 100 includes PCB 110, M.2 connector 112, WLAN card 120, and M.2 device cage 130. WLAN card 120 includes a coaxial cable connector 122. Coaxial connector 122 represents a socket in which a coaxial cable 124 (shown in FIG. 1B) is mounted. Cage 130 includes a support 132, a cover 135, and a retaining screw 136. Support 132 provides rigid support for WLAN card 120 at an end of the WLAN card opposite connector 112 and is typically made of a metallic material to provide a ground connection between the WLAN card and the ground plane of PCB 110.

[0014] In the assembly component 100, the connector 112 is attached to the PCB 110 in a previous assembly operation such as a surface mount process or the like. Additionally, the support 132 can be pre-mounted to a predetermined position on the PCB or can be mounted to that position when assembling the component 100. In either case, a technician installs the coaxial cable 124 into the coaxial connector 122. Then, the technician inserts the WLAN card 120 into the connector 112. When properly positioned, the notch in the end of the WLAN card 120 is co-located with the support 132, and the cover 135 can be placed on top of the WLAN card, with the screw holes aligned with the support. Finally, the screw 136 is placed into the screw hole of the cover 135 and tightened into the support 132. In this way, the WLAN card 120 is firmly inserted into the connector 112 and fixed to the PCB 110. Additionally, the coaxial cable 124 is fixed by the cover 135 such that the coaxial cable cannot be disconnected from the coaxial connector 122.

[0015] The inventors of the present disclosure have understood that, as described above, the assembly steps required to assemble an M.2 WLAN card to a PCB are complex, time-consuming, and prone to failure. Specifically, the component 100 requires three (3) parts (a support, a cover, and a screw) to mount the WLAN card. Such a parts count represents a burden on the inventory system for manufacturing or repairing an information handling system having such a component. Additionally, the time required to mount the bracket, insert the coaxial cable into the coaxial connector, insert the WLAN card into the connector, place the cover on the WLAN card, and install and tighten the screw is very long and increases the assembly and repair costs. For example, the inventors of the present disclosure have found that such an assembly process typically takes more than 100 seconds. Finally, a typical coaxial cable / coaxial connector pair of an M.2 WLAN card can be damaged when installed incorrectly. For example, misalignment of the coaxial cable with the coaxial connector may crush the delicate contact elements within the coaxial cable or the coaxial connector. If the coaxial cable is damaged, the entire antenna assembly may need to be replaced, and a damaged coaxial connector may not be repairable on the WLAN card, resulting in the WLAN card being inoperable. Therefore, the inventors of the present disclosure have understood that a simpler, faster, and less failure-prone mechanism for securing an M.2 WLAN card to a PCB is highly desirable.

[0016] Figure 2An embodiment of an M.2 device mounting assembly 200 is shown. Similar to assembly 100, assembly 200 represents a mounting arrangement for mounting an M.2 device and includes a PCB 210, an M.2 connector 212 similar to connector 112, a WLAN card 220 similar to WLAN card 120, and an M.2 device cage 230. The WLAN card 220 includes a coaxial cable connector 22 in which a coaxial cable 224 (shown in FIG. 4 as described below) is mounted. The cage 230 is a one-piece cage configured to allow the installation of the WLAN card 220 in an open position, as described below, and in a closed position, to hold the WLAN card similar to the hold provided by cage 130, as described below.

[0017] Figure 3A The cage 230 in the open position is shown. The cage 230 includes a base portion 232 having a support holder 233 and a metal ground contact 234, and a cover portion 235 having a positioning stud 236, a knob 237, and a coaxial cable mount 238. The base portion 232 and the cover portion 235 are connected by a strap 239. The base portion 232 provides rigid support for the WLAN card 220 at the end of the WLAN card opposite the connector 212. The support holder 233 provides a holder mechanism whereby the cage 230 is fixed to the PCB 210 through a hole in the PCB and holds the cage firmly to the PCB. The metal ground contact 234 provides a ground connection between the WLAN card and the ground plane of the PCB 110. The cover portion 235 provides a function similar to that of cover 135 and is closable (as shown below Figure 3B to secure the WLAN card 220 to the PCB 210 and hold the coaxial cable firmly in place. However, the cover portion 235 provides an additional function. Specifically, the coaxial cable mount 238 provides a fitting into which the coaxial cable is inserted and is fixed and keyed in a position that ensures proper alignment with the coaxial connector on the WLAN card 220, as described further below.

[0018] Figure 3BShows the cage 230 in the closed position. When the coaxial cable is inserted and fixed and the WLAN card 220 is installed, the cover portion 235 is folded to engage the positioning stud 236 into the guiding retainer in the support portion 232 and is pressed back into place such that the positioning stud is fully inserted into the guiding hole. The action of fully inserting the positioning stud 236 into the guiding hole of the support portion 232 serves to connect the coaxial cable to the coaxial connector of the WLAN card 220, as further described below. In a particular embodiment, the positioning stud 236 includes a retaining mechanism such that when fully inserted into the guiding hole of the support portion 232, the cover 235 is locked in place. For example, the positioning stud 236 may include a retaining ridge that widens the diameter of the positioning stud at the end of the positioning stud, and the retaining ridge may engage a retaining ridge at the bottom of the guiding hole to keep the cover portion 235 from disengaging from the support portion 232. In another example, a retaining groove may be formed at the bottom of the guiding hole, and the retaining groove is complementary to the retaining ridge to hold the cover 235. The knob 237 is used as a surface to firmly press the positioning stud 236 into the guiding hole of the support portion 232 and to grip as needed or desired to disengage the cover 235 from the support portion, thereby repairing or replacing the WLAN card 220.

[0019] Figures 4A to 4G Shows a method for utilizing the cage 230. In Figure 4A , the coaxial cable 224 is located above the cover portion 235 and is installed into the Figure 4B coaxial cable mount 238 in. The coaxial cable 224 is pulled into the corresponding coaxial cable mount 238 to lock the coaxial cable in the Figure 4C predetermined position in. Figure 4D Shows the cage 230 mounted on the PCB 210. The WLAN card 220 is inserted into the Figure 4E connector 212 in, and the cover portion 235 is closed in the Figure 4F to hold the WLAN card 220 and to insert the coaxial cable 224 into the coaxial connector of the WLAN card. Figure 4G Shows a side view of the assembly 200, where the WLAN card 220 is inserted into the connector 212 and the cage 230 is closed. The connector 212 is shown to have a height of 8.5 mm, and the support portion 232 has a height commensurate with the height of the connector.

[0020] Figure 5Component 500 similar to component 200 is shown. Connector 512 is mounted to PCB 510, and WLAN card 520 is inserted into the connector. A cage 530 similar to cage 230 is attached to PCB 500 and is closed to hold WLAN card 520. Connector 512 is shown as having a height of 4.0 mm, and support portion 532 has a height commensurate with the height of the connector. Other connector heights and support heights can be used as needed or desired.

[0021] Figure 6 A generalized implementation of an information handling system 600 is shown. For purposes of this disclosure, an information handling system can include any instrument or collection of instruments operable to compute, classify, process, transmit, receive, retrieve, generate, 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 system 600 can be a personal computer, laptop computer, smart phone, tablet device, or other consumer electronic device, a network server, network storage device, switch, router, or other network communication device, or any other suitable device, and can vary in size, shape, performance, functionality, and price. Additionally, information handling system 600 can include processing resources for executing machine-executable code, such as a central processing unit (CPU), programmable logic array (PLA), an embedded device such as a system on a chip (SoC), or other control logic hardware. Information handling system 600 can also include one or more computer-readable media for storing machine-executable code, such as software or data. Additional components of information handling system 600 can include one or more storage devices that can store machine-executable code, one or more communication ports for communicating with external devices, and various input and output (I / O) devices, such as a keyboard, mouse, and video display. Information handling system 600 can also include one or more buses operable to transfer information between the various hardware components.

[0022] An information handling system 600 may include devices or modules embodying one or more of the devices or modules described below, and operate to perform one or more of the methods described below. The information handling system 600 includes 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 / unified 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 additional resources 674, a trusted platform module (TPM) 676, a network interface 680, a management device 690, and a power supply 695. The processors 602 and 604, the I / O interface 610, the memories 620, the graphics interface 630, the BIOS / UEFI module 640, the disk controller 650, the HDD 654, the ODD 656, the disk emulator 660, the SSD 664, the I / O bridge 670, the additional resources 674, the TPM 676, and the network interface 680 operate together to provide a host environment for the information handling system 600, and the host environment operates to provide data processing functions for 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, etc., to perform data processing tasks associated with the information handling system 600.

[0023] In the host environment, processor 602 is connected to I / O interface 610 via a processor interface 606, and processor 604 is connected to the I / O interface via a 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 video display output 636 to a video display 634. In a particular embodiment, the information handling system 600 includes separate memories dedicated to each of processors 602 and 604 via separate memory interfaces. Examples of memories 620 and 625 include random access memory (RAM) (such as static RAM (SRAM), dynamic RAM (DRAM), non-volatile RAM (NV-RAM), etc.), read-only memory (ROM), another type of memory, or a combination thereof.

[0024] The BIOS / UEFI module 640, the disk controller 650, and the I / O bridge 670 are connected to the I / O interface 610 via the I / O channel 612. Examples of the I / O channel 612 include a Peripheral Component Interconnect (PCI) interface, an Extended PCI (PCI-X) interface, a High-Speed PCI-Express (PCIe) interface, another industry standard or proprietary communication interface, or a combination thereof. The I / O interface 610 may 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. The BIOS / UEFI module 640 includes BIOS / UEFI code that is operable to detect resources within the information handling system 600, provide drivers for the resources, initialize the resources, and access the resources. The BIOS / UEFI module 640 includes code that operates to detect resources within the information handling system 600, provide drivers for the resources, initialize the resources, and access the resources.

[0025] The disk controller 650 includes a disk interface 652 that connects the disk controller to the HDD 654, the ODD 656, and the disk emulator 660. Examples of the disk interface 652 include 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. The disk emulator 660 allows the SSD 664 to be connected to the information handling system 600 via an external interface 662. Examples of the external interface 662 include a USB interface, an IEEE 2394 (FireWire) interface, a proprietary interface, or a combination thereof. Alternatively, the solid-state drive 664 may be disposed within the information handling system 600.

[0026] The I / O bridge 670 includes a peripheral interface 672 that connects the I / O bridge to the additional resources 674, the TPM 676, and the network interface 680. The peripheral interface 672 may be the same type of interface as the I / O channel 612 or may be a different type of interface. Thus, when the peripheral interface 672 is the same type as the I / O channel, the I / O bridge 670 extends the capabilities of the I / O channel 612, and when they are different types, the I / O bridge converts information from a format suitable for the I / O channel to a format suitable for the peripheral channel 672. The additional resources 674 may include a data storage system, an additional graphics interface, a Network Interface Card (NIC), a sound / video processing card, another additional resource, or a combination thereof. The additional resources 674 may be located on the main circuit board, on a separate circuit board or an additional card disposed within the information handling system 600, on a device external to the information handling system, or a combination thereof.

[0027] Network interface 680 represents a NIC that is 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), at another suitable location, or a combination thereof. Network interface device 680 includes network channels 682 and 684 that provide an interface to devices 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 converts information from a format suitable for the peripheral channel to a format suitable for the external device. Examples of network channels 682 and 684 include InfiniBand channels, Fibre Channel channels, Gigabit Ethernet channels, proprietary channel architectures, or a combination thereof. Network channels 682 and 684 may be connected to external network resources (not shown). The network resources may include another information handling system, a data storage system, another network, a grid management system, another suitable resource, or a combination thereof.

[0028] The management device 690 represents one or more processing devices, such as a dedicated baseboard management controller (BMC) system-on-chip (SoC) device, one or more associated memory devices, one or more network interface devices, a complex programmable logic device (CPLD), etc., and the one or more processing devices operate together to provide a management environment for the information handling system 600. Specifically, the 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, etc.) to provide an out-of-band (OOB) mechanism to retrieve information related to the operation of the host environment, provide BIOS / UEFI or system firmware updates, and manage non-processing components of the information handling system 600 (such as system cooling fans and power supplies). The management device 690 may include a network connection to an external management system, and the management device can communicate with the management system to report status information of the information handling system 600, receive BIOS / UEFI or system firmware updates, or perform other tasks for managing and controlling the operation of the information handling system 600. The management device 690 can operate on a power plane separate from the components of the host environment, such that when the information handling system is otherwise shut down, the management device receives power for managing the information handling system 600. Examples of the management device 690 include commercially available BMC products or other devices that operate according to the Intelligent Platform Management Interface (IPMI) specification, the Web Services Management (WSMan) interface, the Redfish application programming interface (API), another Distributed Management Task Force (DMTF) or other management standards, and may include an integrated Dell Remote Access Controller (iDRAC), an embedded controller (EC), etc. As needed or desired, the management device 690 may also include associated memory devices, logic devices, security devices, etc.

[0029] Although only several exemplary embodiments are described in detail herein, those skilled in the art will readily appreciate that many modifications can be made 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 appended claims. In the claims, the means-plus-function clauses are intended to cover the structures described herein as performing the recited function, including not only structural equivalents but also equivalent structures.

[0030] The subject matter disclosed above will be regarded as illustrative and not restrictive, and the appended claims are intended to cover any and all such modifications, enhancements, and other embodiments falling within the scope of the present invention. Accordingly, to the fullest extent permitted by law, the scope of the present invention is determined by the broadest permissible interpretation of the appended claims and their equivalents, and shall not be limited or restricted by the foregoing detailed description.

Claims

1. A device holder for holding an M.2 device to a printed circuit board, the device holder comprising: A support portion configured to be attached to the printed circuit board and provide a support for the first end of the M.2 device thereon; A cover portion; And A strap configured to hold the support portion to the cover portion; Wherein the cover portion is configured to allow the second end of the M.2 device to be inserted into an M.2 connector in an open position and hold the M.2 device to the support portion in a closed position.

2. The device holder according to claim 1, wherein the cover portion includes a cable mount for mounting a cable to be electrically coupled to the M.2 device.

3. The device holder according to claim 2, wherein the cable mount is configured to mount a coaxial cable to the cover portion.

4. The device holder according to claim 3, wherein the cable mount is further configured to position the coaxial cable such that when the cover portion is in the closed position, the coaxial cable is coupled to a coaxial connector of the M.2 device.

5. The device holder according to claim 1, wherein the cover portion further includes positioning studs, and the support portion includes guide holes to receive the positioning studs when the cover portion is in the closed position.

6. The device holder according to claim 5, wherein the positioning studs include a first retaining ridge to lock the cover portion in the closed position.

7. The device holder according to claim 6, wherein the guide holes include a second retaining ridge to engage the first retaining ridge to lock the cover portion.

8. The device holder according to claim 6, wherein the guide holes include a retainer complementary to the first retaining ridge to engage the first retaining ridge to lock the cover portion.

9. The device holder according to claim 1, wherein the support portion includes a support retainer to fix the device holder to the printed circuit board.

10. The device holder according to claim 1, wherein the cover portion includes a knob for opening and closing the cover portion.

11. A method for holding an M.2 device to a printed circuit board, the method comprising: Fixing a support portion of a device holder to the printed circuit board, the device holder including a cover portion and a strap for holding the support portion to the cover portion; Inserting a first end of the M.2 device into an M.2 connector when the cover portion is in an open position, wherein a second end of the M.2 device is disposed on the support portion; And Closing the cover portion to hold the M.2 device to the support portion.

12. The method according to claim 11, wherein the cover portion includes a cable mount for mounting a cable to be electrically coupled to the M.2 device.

13. The method according to claim 12, wherein the cable mount is configured to mount a coaxial cable to the cover portion.

14. The method according to claim 13, wherein the cable mount is further configured to position the coaxial cable such that when the cover portion is in the closed position, the coaxial cable is coupled to the coaxial connector of the M.2 device.

15. The method according to claim 11, wherein the cover portion further includes positioning studs, and the support portion includes guide holes to receive the positioning studs when the cover portion is in the closed position.

16. The method according to claim 15, wherein the positioning stud includes a first retaining ridge to lock the cover portion in the closed position.

17. The method according to claim 16, wherein the guide hole includes a second retaining ridge to engage the first retaining ridge to lock the cover portion.

18. The method according to claim 16, wherein the guide hole includes a retainer that is complementary to the first retaining ridge to engage the first retaining ridge to lock the cover portion.

19. The method according to claim 11, wherein the support portion includes a support retainer to secure the device holder to the printed circuit board.

20. A printed circuit board, comprising: an M.2 connector attached to the printed circuit board and configured to connect to a first end of an M.2 device; and a device holder for holding the M.2 device to the printed circuit board, the device holder including: a support portion configured to be attached to the printed circuit board and provide a support on which a second end of the M.2 device can be placed; a cover portion; and a band configured to hold the support portion to the cover portion; wherein the cover portion is configured to allow the M.2 device to be inserted into the M.2 connector in an open position and hold the M.2 device to the support portion in a closed position.

Images