Computing devices are getting smaller, thinner, and lighter. Many circuit module designers are creating circuit modules for such computing devices with improvements in features (e.g., improved power management), but without modifications to or improvements in the physical size, shape, or configuration. For example, memory technologies continue to improve, but system designers for laptops, ultrabooks, netbooks, tablets, smart phones, and other compact and/or handheld computing devices are limited to small outline dual in-line memory modules (SODIMM) or some form of memory down.
Systems with “memory down” include memory chips that are mounted directly onto a circuit board (via, for example, soldering). Memory down systems lack platform flexibility and serviceability. An end-user cannot upgrade the amount of memory contained within a system using memory down. Furthermore, manufacturers producing memory down systems cannot swap out bad memory chips, resulting in decreased product yield.
SODIMMs are memory modules with smaller dimensions than standard DIMMs. The modularity of SODIMMs offers flexibility: manufacturers can offer systems with different configurations, and users can often upgrade systems with SODIMMs. However, the relatively large size of SODIMMs limits how compact computing devices can be made.
The following description includes discussion of figures having illustrations given by way of example of implementations of embodiments of the invention. The drawings should be understood by way of example, and not by way of limitation. As used herein, references to one or more “embodiments” are to be understood as describing a particular feature, structure, or characteristic included in at least one implementation of the invention. Thus, phrases such as “in one embodiment” or “in an alternate embodiment” appearing herein describe various embodiments and implementations of the invention, and do not necessarily all refer to the same embodiment. However, they are also not necessarily mutually exclusive. In the following description and claims, the term “coupled” and its derivatives may be used. The term “coupled” herein may refer to two or more elements which are in direct contact (physically, electrically, magnetically, optically, etc.), or to two or more elements that are not in direct contact with each other, but which still interact with each other.
Embodiments of the invention relate to a system, circuit module, and circuit module connector with a third set of contacts. Connectors connect circuit modules to other circuit modules or boards (e.g., main boards, or other modules, cards, or boards). In particular, embodiments relate to card-edge connectors, which connect a circuit card to other circuit modules or boards via an edge of the circuit card. In one example, a memory connector connects a memory module to a main board (i.e., motherboard) via two sets of opposing contacts on one section of the connector, and a third set of contacts on another section of the connector.
According to one embodiment, the connector includes one or more rigid supports to connect the two sections of the connector, and/or to aid with strength and alignment of contacts. The connector can also include one or more retention mechanisms to secure the circuit module to the connector.
In one embodiment, the circuit module connector and corresponding circuit modules enable flexibility and scalability, while enabling compact form factors and increased contact space.
In the following description, numerous details are discussed to provide a more thorough explanation of embodiments of the present invention. It will be apparent, however, to one skilled in the art, that embodiments of the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring embodiments.
Note that in the corresponding drawings of the embodiments, signals are represented with lines. Some lines may be thicker, to indicate more constituent signal paths, and/or have arrows at one or more ends, to indicate primary information flow direction. Such indications are not intended to be limiting. Rather, the lines are used in connection with one or more exemplary embodiments to facilitate easier understanding of a circuit or a logical unit. Any represented signal, as dictated by design needs or preferences, may actually comprise one or more signals that may travel in either direction and may be implemented with any suitable type of signal scheme.
Embodiments of the invention include first and second sets of opposing contacts on a first section of the connector. Contacts are areas providing an electrical connection between two circuits or circuit components (e.g., between a circuit module and a circuit board). Contacts can include pins (e.g., pins which are arched to enable compression and to generate tension when in contact with corresponding contacts, straight pins, or any other type and/or shape of pins), or any other conductive contacts providing an electrical connection. The first and second sets of opposing contacts are to contact corresponding first and second sets of contacts on opposite surfaces of a circuit module. For example, connectors 100a and 100b include two sets of opposing contacts 104 on a first section 106 of the connector to contact corresponding sets of contacts on a circuit module (e.g., circuit module 200a of
The connector includes a third set of contacts on a second section of the connector; the third set of contacts is to contact a corresponding third set of contacts on one of the surfaces of the circuit module. For example, connectors 100a and 100b include a third set of contacts 108 on a second section 110 of the connectors 100a and 100b. In one embodiment, a slot on the first section 106 is to accept a first edge of a circuit module, and the second section 110 is to contact a second edge of the circuit module opposite to the first edge. According to one embodiment, the third set of contacts 108 includes arched pins. Arched pins can enable improved contact with the corresponding contacts on the circuit module.
In one embodiment, the third set of contacts 108 is unopposed (e.g., the third set of contacts 108 does not have a set of contacts opposite to the set). According to one embodiment, a connector with a third set of contacts increases available pin counts, enabling more compact form factors.
In another embodiment, the connector includes a fourth set of contacts (not shown) opposing the third set of contacts 108. For example, a third section of the connector that clamps down over a circuit module over the second section 110 of the connector can include a fourth set of contacts; the fourth set of contacts is to contact a corresponding fourth set of contacts on a surface of the circuit module. In one such example, the third section of the connector extends the length of the connector to provide the fourth set of contacts with a similar or equal number of contacts as the third set of contacts. In another example, the third and fourth sets of contacts are located on a removable section into which a circuit module is first inserted (e.g., resembling the arrangement of contacts on the first section 106 as illustrated in
The first and second sets of opposing contacts 104 and the third set of contacts 108 are illustrated as continuous rows of contacts; however, each set of contacts can be non-continuous (e.g., include gaps), or be arranged in different configurations. Additionally, although the first and second sections are illustrated as two opposing sides, connectors can include other shapes and/or configurations. For example, the connector could include a third set of contacts on an adjacent side (e.g., where the rigid supports 112a and/or 112b are illustrated). In another example, the connector includes the first and second sets of opposing contacts along two sides of a triangular configuration, and the third set of contacts is on the third side of the triangular configuration.
Connectors 100a and 100b include connector housing 102. The connector housing 102 can be made from any suitable housing material, such as plastic, a resin, a polymer, or any other any material providing sufficient electrical insulation. The connector housing 102 can be formed from a single piece (e.g., via injection molding, three dimensional (3D) printing, or any other method of forming a single piece), or formed from two or more pieces. When formed from two or more pieces, the pieces can be assembled in any way known in the art. For example, the pieces can be assembled via fastening (e.g., with screws or other fasteners), adhesives, welding of the pieces, or by any other method of assembling the pieces.
As illustrated, connector housing 102 includes two rigid supports 112a and 112b connecting the first section 106 of the connector with the second section 110 of the connector. In other embodiments, zero, one, or more rigid supports can connect the sections of the connector. For example, in one embodiment, a rigid frame around the first and second sections provides support. In another example, the connector includes a rigid support connecting inner portions of the first section 106 and the second section 110. Rigid supports can provide strength and stability (e.g., during manufacture, test, shipping, installation, or any other circumstances in which the connector may be handled or moved). The embodiment illustrated in
According to embodiments of the invention, a circuit module includes first and second sets of contacts on opposite surfaces of the circuit module to contact corresponding first and second sets of opposing contacts on a first section of a connector. For example, circuit modules 200a-200c each include a first set of contacts 201 on a top surface 202, and a second set of contacts 203 on a bottom surface 204 of the circuit module.
The circuit modules 200a-200c also each include a third set of contacts on the bottom surface of the circuit module to contact a corresponding third set of contacts on a connector. For example, circuit modules 200a-200c each include a third set of contacts 205 on surface 204. The circuit modules 200a-200c are to be connected to circuit boards via connectors (e.g., connector 100a of
Any number of contacts can be included on circuit modules 200a-200c; the number of possible contacts is determined based on circuit module dimensions (e.g., height and width), contact pitch, and/or available edge space. In one embodiment, the circuit module is approximately 31 mm wide and has a height of approximately 15 mm. In one such embodiment, pins having a pitch of 0.45 mm can result in a configuration with 189 pins. In another embodiment, the circuit module is approximately 34 mm wide and has a height of 15 mm. In one such embodiment, pins having a pitch of 0.5 mm can result in a configuration with 179 pins.
The circuit module can be any type of circuit module using a connector, for example, a memory module, a graphics card, a processor, or any other circuit module and/or card. A memory module can include, for example, a dual inline memory module (DIMM) comprising a third set of contacts (e.g., the third set of contacts 205).
As illustrated, circuit modules 200a-200c include areas 206a and 206b, which can include printed circuitry, mounted circuit chips, and/or other components. For example, areas 206a and 206b can include DRAMs, processing units, graphics processors, caches, termination resistors, buses, and/or any other circuit chip or component. In one example, areas 206a and 206b each include a DRAM chip (e.g., a 32b DRAM chip). Although two areas are illustrated, any number of chips or components can be included in any configuration on the surfaces of circuit modules 200a-200c. For example, although the bottom surface 204 is illustrated as including no areas for chips or other circuitry, either of the surfaces 202 and 204, or both of the surfaces 202 and 204 can include circuitry and/or components.
Circuit modules and connectors also include retention and/or alignment mechanisms. In one embodiment, a circuit module includes one or more holes, to accept one or more protrusions 117 on a connector. For example, circuit modules 200a and 200c includes holes 210a and 210b. The holes 210a and 210b are to, for example, align the sets of contacts on the circuit module to the corresponding sets of contacts on the connector. The holes 210a and 210b and corresponding protrusions 117 on connectors can also aid in retaining the circuit modules 200a and 200c on a connector. The one or more protrusions 117 on the connector can include various shapes to improve guidance and/or secure the circuit module to the connector. For example, a protrusion can include a tapered shape (e.g., a cone shape), which enables easy initial insertion due to a narrow upper portion, and then allows the circuit module to align with the connector as the circuit module slides down the tapered protrusion onto a wider base of the protrusion.
The one or more protrusions can be disposed on rigid supports of the connector (e.g., rigid supports 112a and 112b of
Although two holes are illustrated, circuit modules can include any number of holes (e.g., zero, one, or more holes), in any configuration. Furthermore, although holes are illustrated in
In one embodiment, a circuit module includes one or more notches to aid in aligning the contacts of the circuit module with the contacts of the connector. For example, circuit module 200a includes notches 208a and 208b, which align with corresponding keys on a connector.
According to one embodiment, a circuit module includes a hole to align with a second hole 115 on a connector; the hole and the second hole 115 are to accept a screw to aid in retaining the circuit module on the connector. For example, circuit module 200b of
In one embodiment, a circuit module includes areas onto which a section of a connector applies force. For example, circuit modules 200c of
In one embodiment, a circuit board (e.g., a main board of a computing device), includes a connector, which is to accept a circuit module. For example, the system 300 includes a circuit board 302, a connector 304, and a circuit module 306. The connector 304 is to connect the circuit module 306 to the circuit board 302. The circuit module 306 and connector 304 can include any of the embodiments described herein. The connector includes first and second sets of opposing contacts on a first section 308 of the connector; the first and second sets of opposing contacts are to contact corresponding first and second sets of contacts on opposite surfaces of the circuit module 306 (e.g., the contacts on the first section 308 of the connector 304 are to contact contacts on the top and bottom surfaces along the edge 312 of the circuit module 306).
The connector also includes a third set of contacts on a second section 310 of the connector 304; the third set of contacts is to contact a corresponding third set of contacts on one of the surfaces of the circuit module (e.g., the contacts on the second section 310 of the connector 304 are to contact contacts on the bottom surface along the edge 314 of the circuit module 306.).
In one embodiment, the circuit module 306 is to be inserted at an angle into the connector 304 on the circuit board 302. One such embodiment includes a “right-angle” connector. For example, a first edge 312 of the circuit module 306 is to be inserted at an angle into a slot on the first section 308 of the connector. The second edge 314 of the circuit module is then to be lowered onto the third set of pins on the second section 310 of the connector 304. In one such embodiment, the circuit module 306 snaps into place onto the connector 304. The third set of contacts on the bottom surface of circuit module 306 is to contact the third set of contacts on the connector 304. In one such embodiment, the inserted circuit module and the connector are to be disposed substantially coplanar (e.g., substantially parallel) with the circuit board 302. The coplanar arrangement of the system 300 enables a low profile suitable for compact computing devices. For example, an implementation where the circuit module 306 has circuit components on a single surface (e.g., the top surface of the circuit module 306 which is visible in system diagram 300), the coplanar arrangement enables the system to achieve a Z-height of 3-3.5 mm.
System 400 represents a computing device in accordance with any embodiment described herein, and can be a laptop computer, a desktop computer, a server, a gaming or entertainment control system, a scanner, copier, printer, or other electronic device. One or more components of system 400 can include connectors and/or circuit modules in accordance with embodiments described herein. It will be understood that certain of the components are shown generally, and not all components of a computing system are shown in system 400. System 400 includes processor 420, which provides processing, operation management, and execution of instructions for system 400. Processor 420 can include any type of microprocessor, central processing unit (CPU), processing core, or other processing hardware to provide processing for system 400. Processor 420 controls the overall operation of system 400, and can include one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or the like, or a combination of such devices.
Memory subsystem 430 can represent main memory, cache, or any other memory (e.g., any device providing storage for code to be executed by processor 420 or data values) for system 400. Memory subsystem 430 includes memory 432, which represents one or more memory devices that can include read-only memory (ROM), flash memory, one or more varieties of random access memory (RAM), or other memory devices, or a combination of such devices. Processor 420 includes a memory controller 434, which can control read and write operations to and from memory 432. In one embodiment, memory subsystem 430 includes memory controller 434. In one embodiment, memory subsystem 430 is located on processor 420. In another embodiment, memory subsystem 430 is located on a separate device. In yet another embodiment, one or more parts of memory subsystem 430 are located on processor 420 and other parts of memory subsystem 430 are located on a separate device. In one embodiment, memory 432 could be designed as a cache and included as part of processor 420.
Memory subsystem 430 can store and host, among other things, operating system (OS) 436 to provide a software platform for execution of instructions in system 400. Additionally, other program instructions 438 are stored and executed from memory subsystem 430 to provide the logic and the processing of system 400. OS 436 and program instructions 438 are executed by processor 420.
Processor 420 and memory subsystem 430 are coupled to bus/bus system 410. Bus 410 is an abstraction that represents any one or more separate physical buses, communication lines/interfaces, and/or point-to-point connections, connected by appropriate bridges, adapters, and/or controllers. Therefore, bus 410 can include, for example, one or more of a system bus, a Peripheral Component Interconnect (PCI) bus, a HyperTransport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB), or an Institute of Electrical and Electronics Engineers (IEEE) standard 1394 bus (commonly referred to as “Firewire”). The buses of bus 410 can also correspond to interfaces in network interface 450.
In one embodiment, bus 410 includes a data bus that is a data bus included in memory subsystem 430 over which processor 420 can read values from memory 432. The additional line shown linking processor 420 to memory subsystem 430 represents a command bus over which processor 420 provides commands and addresses to access memory 432.
System 400 also includes one or more input/output (I/O) interface(s) 440, network interface 450, one or more internal mass storage device(s) 460, and peripheral interface 470 coupled to bus 410. I/O interface 440 can include one or more interface components through which a user interacts with system 400 (e.g., video, audio, and/or alphanumeric interfacing). Network interface 450 provides system 400 the ability to communicate with remote devices (e.g., servers, other computing devices) over one or more networks. Network interface 450 can include an Ethernet adapter, wireless interconnection components, USB (universal serial bus), one or more antennae, or other wired or wireless standards-based or proprietary interfaces.
Storage 460 can be or include any conventional medium for storing large amounts of data in a nonvolatile manner, such as one or more magnetic, solid state, or optical based disks, or a combination. Storage 460 holds code or instructions and data 462 in a persistent state (i.e., the value is retained despite interruption of power to system 400). Storage 460 can also be generically considered to be a “memory.” Whereas storage 460 is nonvolatile, memory 432 can include volatile (i.e., the value or state of the data is indeterminate if power is interrupted to system 400) and/or non-volatile memory.
Peripheral interface 470 can include any hardware interface not specifically mentioned above. Peripherals refer generally to devices that connect dependently to system 400. A dependent connection is one where system 400 provides the software and/or hardware platform on which operation executes, and with which a user interacts.
Various components described herein can be a means for performing the operations or functions described. Each component described herein includes software, hardware, or a combination of these. The components can be implemented as software modules, firmware modules, hardware modules, special-purpose hardware (e.g., application specific hardware, application specific integrated circuits (ASICs), digital signal processors (DSPs), or other special-purpose hardware), embedded controllers, hardwired circuitry, or as any combination of software, firmware, and/or hardware.
Device 500 represents a mobile computing device, such as a computing tablet, a mobile phone or smartphone, a wireless-enabled e-reader, or other mobile device. One or more components of system 400 can include connectors and/or circuit modules in accordance with embodiments described herein. It will be understood that certain of the components are shown generally, and not all components of such a device are shown in device 500.
Device 500 includes processor 510, which performs the primary processing operations of device 500. Processor 510 can include one or more physical devices, such as microprocessors, application processors, microcontrollers, programmable logic devices, or other processing means. In one embodiment, processor 510 includes optical interface components in addition to a processor die. Thus, the processor die and photonic components are in the same package. Such a processor package can interface optically with an optical connector in accordance with any embodiment described herein.
The processing operations performed by processor 510 include the execution of an operating platform or operating system on which applications and/or device functions are executed. The processing operations include operations related to I/O (input/output) with a human user or with other devices, operations related to power management, and/or operations related to connecting device 500 to another device. The processing operations can also include operations related to audio I/O and/or display I/O.
In one embodiment, device 500 includes audio subsystem 520, which represents hardware (e.g., audio hardware and audio circuits) and software (e.g., drivers, codecs) components associated with providing audio functions to the computing device. Audio functions can include speaker and/or headphone output, as well as microphone input. Devices for such functions can be integrated into device 500, or connected to device 500. In one embodiment, a user interacts with device 500 by providing audio commands that are received and processed by processor 510.
Display subsystem 530 represents hardware (e.g., display devices) and software (e.g., drivers) components that provide a visual and/or tactile display for a user to interact with the computing device. Display subsystem 530 includes display 532, which includes the particular screen or hardware device used to provide a display to a user. In one embodiment, display 532 includes logic separate from processor 510 to perform at least some processing related to the display. In one embodiment, display subsystem 530 includes a touchscreen device that provides both output to and input from a user.
I/O controller 540 represents hardware devices and software components related to interaction with a user. I/O controller 540 can operate to manage hardware that is part of audio subsystem 520 and/or display subsystem 530. Additionally, I/O controller 540 illustrates a connection point for additional devices that connect to device 500 through which a user might interact with the system. For example, devices that can be attached to device 500 might include microphone devices, speaker or stereo systems, video systems or other display device, keyboard or keypad devices, or other I/O devices for use with specific applications such as card readers or other devices.
As mentioned above, I/O controller 540 can interact with audio subsystem 520 and/or display subsystem 530. For example, input through a microphone or other audio device can provide input or commands for one or more applications or functions of device 500. Additionally, audio output can be provided instead of or in addition to display output. In another example, if display subsystem 532 includes a touchscreen, the display device also acts as an input device, which can be at least partially managed by I/O controller 540. There can also be additional buttons or switches on device 500 to provide I/O functions managed by I/O controller 540.
In one embodiment, I/O controller 540 manages devices such as accelerometers, cameras, light sensors or other environmental sensors, gyroscopes, global positioning system (GPS), or other hardware that can be included in device 500. The input can be part of direct user interaction, as well as providing environmental input to the system to influence its operations (such as filtering for noise, adjusting displays for brightness detection, applying a flash for a camera, or other features).
Memory subsystem 560 includes memory 562 for storing information in device 500. Memory 562 can include non-volatile (state does not change if power to the memory device is interrupted) and/or volatile (state is indeterminate if power to the memory device is interrupted) memory devices. Memory 562 can store application data, user data, music, photos, documents, or other data, as well as system data (whether long-term or temporary) related to the execution of the applications and functions of system 500. Processor 510 includes a memory controller 564, which can control read and write operations to and from memory 562. In one embodiment, memory subsystem 560 includes the memory controller 564. In one embodiment, memory subsystem 560 is located on processor 510. In another embodiment, memory subsystem 560 is located on a separate device. In yet another embodiment, one or more parts of memory subsystem 560 are located on processor 510 and other parts of memory subsystem 560 are located on a separate device. In one embodiment, memory 562 is designed as caches and included as part of processor 510.
In one embodiment, device 500 includes power management 550 that manages battery power usage, charging of the battery, and features related to power saving operation. Power management 550 can initiate a transition between two or more power states for system 500, or for select sub-parts of system 500.
Connectivity 570 includes hardware devices (e.g., wireless and/or wired connectors, one or more antennae, and/or communication hardware) and software components (e.g., drivers, protocol stacks) to enable device 500 to communicate with external devices. The device could be separate devices, such as other computing devices, wireless access points or base stations, as well as peripherals such as headsets, printers, or other devices.
Connectivity 570 can include multiple different types of connectivity. To generalize, device 500 is illustrated with cellular connectivity 572 and wireless connectivity 574. Cellular connectivity 572 refers generally to cellular network connectivity provided by wireless carriers, such as provided via GSM (global system for mobile communications) or variations or derivatives, CDMA (code division multiple access) or variations or derivatives, TDM (time division multiplexing) or variations or derivatives, LTE (long term evolution—also referred to as “4G”), or other cellular service standards. Wireless connectivity 574 refers to wireless connectivity that is not cellular, and can include personal area networks (such as Bluetooth), local area networks (such as WiFi), and/or wide area networks (such as WiMax), or other wireless communication. Wireless communication refers to transfer of data through the use of modulated electromagnetic radiation through a non-solid medium. Wired communication occurs through a solid communication medium.
Peripheral connections 580 include hardware interfaces and connectors, as well as software components (e.g., drivers, protocol stacks) to make peripheral connections. It will be understood that device 500 could both be a peripheral device (“to” 582) to other computing devices, as well as have peripheral devices (“from” 584) connected to it. Device 500 commonly has a “docking” connector to connect to other computing devices for purposes such as managing (e.g., downloading and/or uploading, changing, synchronizing) content on device 500. Additionally, a docking connector can allow device 500 to connect to certain peripherals that allow device 500 to control content output, for example, to audiovisual or other systems.
In addition to a proprietary docking connector or other proprietary connection hardware, device 500 can make peripheral connections 580 via common or standards-based connectors. Common types can include a Universal Serial Bus (USB) connector (which can include any of a number of different hardware interfaces), DisplayPort including MiniDisplayPort (MDP), High Definition Multimedia Interface (HDMI), Firewire, or other type.
Besides what is described herein, various modifications can be made to the disclosed embodiments and implementations of the invention without departing from their scope. Therefore, the illustrations and examples herein should be construed in an illustrative, and not a restrictive sense. The scope of the invention should be measured solely by reference to the claims that follow.
Number | Name | Date | Kind |
---|---|---|---|
3479634 | Pritulsky | Nov 1969 | A |
3611275 | Leddy | Oct 1971 | A |
3848952 | Tighe, Jr. | Nov 1974 | A |
4222622 | Griffin | Sep 1980 | A |
4603928 | Evans | Aug 1986 | A |
4746299 | Matsuoka | May 1988 | A |
4755146 | Rishworth | Jul 1988 | A |
4938701 | Heberling | Jul 1990 | A |
4993956 | Pickles et al. | Feb 1991 | A |
5112231 | Harwath et al. | May 1992 | A |
5335146 | Stucke | Aug 1994 | A |
5425651 | Thrush et al. | Jun 1995 | A |
6097883 | Dell et al. | Aug 2000 | A |
6179627 | Daly et al. | Jan 2001 | B1 |
6347039 | Lee | Feb 2002 | B1 |
6388886 | Tobita | May 2002 | B1 |
6394817 | Kihira et al. | May 2002 | B1 |
6402556 | Lang et al. | Jun 2002 | B1 |
6425766 | Panella | Jul 2002 | B1 |
6438014 | Funaba et al. | Aug 2002 | B2 |
6585525 | Jung et al. | Jul 2003 | B2 |
6688892 | Fukumoto | Feb 2004 | B2 |
6896561 | Lai | May 2005 | B2 |
7200023 | Foster, Sr. | Apr 2007 | B2 |
7708599 | Guan et al. | May 2010 | B2 |
8002583 | van Woensel | Aug 2011 | B2 |
8684768 | Huang et al. | Apr 2014 | B2 |
20020042223 | Belopolsky et al. | Apr 2002 | A1 |
20020115318 | Apicelli | Aug 2002 | A1 |
20060276075 | Iida et al. | Dec 2006 | A1 |
20070238323 | Mathews et al. | Oct 2007 | A1 |
20080038961 | Park et al. | Feb 2008 | A1 |
20090069081 | Thorner | Mar 2009 | A1 |
20090227146 | Kimura et al. | Sep 2009 | A1 |
20100041276 | Tsai et al. | Feb 2010 | A1 |
20100062624 | Tsai | Mar 2010 | A1 |
20100173527 | Zhou | Jul 2010 | A1 |
20110130041 | Chen et al. | Jun 2011 | A1 |
20110136388 | Fu et al. | Jun 2011 | A1 |
20110151701 | Ngo | Jun 2011 | A1 |
20110151716 | Kondo | Jun 2011 | A1 |
20110176864 | Shin et al. | Jul 2011 | A1 |
20110300759 | Ngo | Dec 2011 | A1 |
20120003849 | Luo | Jan 2012 | A1 |
20120302074 | Hartenstein | Nov 2012 | A1 |
20140094063 | Daly | Apr 2014 | A1 |
20140227911 | Lim et al. | Aug 2014 | A1 |
Number | Date | Country | |
---|---|---|---|
20140094063 A1 | Apr 2014 | US |