Maintaining and protecting the security of a device or system may have a number of benefits. For example, a secure device, operating system, application, and system may be configured to prevent the unauthorized or undesired appropriation (e.g., “hacking”) of data about or from the device, operating system, application, and system. Some systems and devices may include one or more security features and applications. Security features and applications may include encryption and password protecting data.
Some security applications may access a memory. Some security applications may provide communication to and from the application via a data bus or other access point. Generally, from some security perspectives, access to a communication bus and/or a memory to store security data may provide an opportunity to breach the security of a system and device.
The several embodiments described herein are solely for the purpose of illustration. Embodiments may include any currently or hereafter-known versions of the elements described herein. Therefore, persons skilled in the art will recognize from this description that other embodiments may be practiced with various modifications and alterations.
Apparatus 100 includes a printed circuit board (PCB) 105, an integrated circuit (IC) 110 positioned over PCB 105 and electrically connected to PCB 105, and an IC chip 125 positioned between PCB 105 and IC 110. In some embodiments, PCB 105 and IC 110 are arranged in a spaced apart configuration. Apparatus 100 may include a closed boundary barrier 145 between and in contact with PCB 105 and IC 110.
PCB 105 may include one or more levels. The one or more layers may include laminated conductive layers separated and supported by layers of insulating substrates. In some embodiments, the various layers may be connected by vias extending between the various layers.
In some embodiments herein, chip 125 is electrically connected to PCB 110 by one or more pads 130. A PCB pad 135 may provide an electrically conductive connection point to facilitate connecting chip 125 to PCB 105. Chip 125, pads 130, and PCB pads 135 may be contained or otherwise located within an inner confinement area 150 defined by boundary barrier 145. In some embodiments, boundary barrier 145 provides a continuous structure between PCB 105 and IC 110 that separates inner confinement area 150 including chip 125, pads 130, and PCB pads 135 from being accessed from a point exterior to the inner confinement area.
In some embodiments, chip 125, pads 130, and PCB pads 135 are completely surrounded and physically shielded from direct physical contact (e.g., undesired eavesdropping, probing, etc.) by boundary barrier 145. For example, IC 110 may be located over a top of chip 125, PCB 105 may be located below a bottom of chip 125, and boundary barrier 145 may be located outward of lateral sides of chip 125, pads 130, and PCB pads 135. In some embodiments where boundary barrier 145 is between and in contact with PCB 105 and IC 110, the PCB, IC, and boundary barrier may cooperate to physically shield and deny physical access to chip 125, pads 130, and PCB pads 135.
Boundary barrier 145 may be a conductive material. In some embodiments, boundary barrier 145 may include a solder material. In some embodiments, boundary barrier 145 may provide a conductive pathway between PCB 105 and IC 110.
In some embodiments, PCB pads 135 may include a conductive signal trace on a surface of PCB 105, a wire, a data bus, and other electrical conductive connectors. PCB pads 135 may be any number, combination, and variety of communication pathways between PCB 105 and IC 110.
In some embodiments, PCB pads 135 (e.g., a data bus) are located entirely within inner confinement area 150. The data bus located in the inner confinement area 150 is physically shielded from the environment outside of the inner confinement area. Accordingly, a communication session between PCB 105, chip 125, and IC 110 may be conducted in an efficient and secure manner.
In some embodiments in accordance herewith, communication between chip 125 and IC 110 may be provided over a communication pathway (e.g., data bus, conductor, trace, etc.) that is physically isolated and, in some aspects, secure. Accordingly, some considerations for encrypting data over a data bus may be lessened or obviated.
In some embodiments, IC 125 may include a security IC. The security IC may have one or more security features incorporated therein. The security IC may include one or more encryption features to encrypt or otherwise enable secure handling of data and information processed by IC 110. For example, the security chip may include instructions and mechanisms for executing cryptographic operations, sensors, etc. In some embodiments, IC 125 may tend to be larger than chip 125, due at least in part to the inclusion of encryption features in the security IC
In some embodiments, boundary barrier 145 may include, incorporate, and/or be associated with one or more integrity mechanisms. The integrity mechanisms (not shown) may provide an indication of a breach, a break, a discontinuity, or another type of compromise and/or degradation of the structural integrity of boundary barrier 145. The integrity mechanisms may include a detector that senses a breach based on a resistive or a capacitive testing process and other types of sensors.
In some embodiments, IC 110 is connected to PCB pad 135 by an inner connector 140. Inner connector 140 may be a conductive pathway, such as, for example, a solder material.
In some embodiments, IC 110 is connected to a PCB conductive trace 120 by an outer connector 115. Outer connector 115 may be a conductive pathway, such as, for example, a solder material. Outer connection 115 may provide a further physical barrier to block physical access to chip 125 and electrical connections to chip 125.
Shown is an embodiment where PCB conductive trace 120 and outer connector 115 are outside of the inner confinement area 150. Accordingly, communication sessions conducted using the PCB conductive trace and the outer connector may be accessible (e.g., not protected or secure).
At operation 300, chip 125 is placed on PCB 105. In some embodiments, the chip may include a memory module. In some embodiments, the chip may be prepared for mounting on PCB 105 prior to positioning operation 300. For example, chip 125 may undergo a thinning process during the manufacture thereof to prepare it for use in process 300.
At operation 310, chip 125 is electrically connected to PCB 105. Chip 125 may be attached to PCB 105 in accordance with a PCB manufacturing process, including, for example, by a trace, a wire, PCB pad 135, a bump, a data bus, and combinations thereof. The electrical connections may provide a communication pathway to the chip.
At operation 315, IC 110 is positioned over PCB 110, chip 125, and the electrical connections to the chip (e.g., 130, 135).
At operation 320, boundary barrier 145 is formed on PCB 105 to completely surround chip 125 and electrical connections 130, 135 to the chip. Boundary barrier 145 is arranged between IC 110 and PCB 105 at locations beyond a lateral extent of the chip and the electrical connections to the chip, as illustrated in
In some embodiments, boundary barrier 145 includes a solder material that may be subjected to a thermal reflow process to attach the boundary barrier to PCB 105. During the reflow process, boundary barrier 145 may be heated to a temperature sufficient to cause the solder of the boundary barrier to flow, thereby facilitating an attachment of the IC to the PCB.
It is noted that the various operations of process 300 may be accomplished in conjunction or in association with other processes and in sequences other than that specifically delineated in
Those in the art should appreciate that system 400 may include additional, fewer, or alternative components to PCB 405, memory chip 425, IC 410, and device 460.
In some embodiments, device 460 may include a subsystem such as, for example, a graphics subsystem, an audio processing subsystem, other specialized processing subsystems, a processor, and discrete components. In an instance device 460 is a memory device 460 may comprise any type of memory for storing data, including but not limited to a Single Data Rate Random Access Memory, a Double Data Rate Random Access Memory, or a Programmable Read Only Memory.
It should be appreciated that the drawings herein are illustrative of various aspects of the embodiments herein, not exhaustive of the present disclosure.
This is a divisional of prior U.S. patent application Ser. No. 11/476,956, filed Jun. 28, 2006 now U.S. Pat. No. 7,633,168.
Number | Name | Date | Kind |
---|---|---|---|
5477082 | Buckley, III et al. | Dec 1995 | A |
5646828 | Degani et al. | Jul 1997 | A |
5896894 | Schwamborn et al. | Apr 1999 | A |
5949135 | Washida et al. | Sep 1999 | A |
5994166 | Akram et al. | Nov 1999 | A |
6147401 | Solberg | Nov 2000 | A |
6404044 | Akram et al. | Jun 2002 | B2 |
6518622 | Chew et al. | Feb 2003 | B1 |
6521480 | Mitchell et al. | Feb 2003 | B1 |
6664643 | Emoto | Dec 2003 | B2 |
6847105 | Koopmans | Jan 2005 | B2 |
6853064 | Bolken et al. | Feb 2005 | B2 |
6936918 | Harney et al. | Aug 2005 | B2 |
6979895 | Akram et al. | Dec 2005 | B2 |
7109576 | Bolken et al. | Sep 2006 | B2 |
7163840 | Chen et al. | Jan 2007 | B2 |
7217993 | Nishimura | May 2007 | B2 |
7329562 | Kumamoto et al. | Feb 2008 | B2 |
20040238934 | Warner et al. | Dec 2004 | A1 |
20060043559 | Chow et al. | Mar 2006 | A1 |
20060263937 | Fukase et al. | Nov 2006 | A1 |
20080111248 | Foong et al. | May 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20100041182 A1 | Feb 2010 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 11476956 | Jun 2006 | US |
Child | 12604697 | US |