|Publication number||US20030084309 A1|
|Application number||US 10/273,718|
|Publication date||1 May 2003|
|Filing date||18 Oct 2002|
|Priority date||22 Oct 2001|
|Also published as||CN1286019C, CN1608249A, DE60211730D1, DE60211730T2, DE60236309D1, DE60237222D1, DE60239227D1, EP1438667A2, EP1438667B1, EP1438818A2, EP1438818B1, EP1442355A2, EP1442355B1, EP1442365A2, EP1442374A2, EP1442374B1, EP1466448A2, EP1466448B1, US6901491, US6938119, US7209996, US7248585, US7865667, US20030081615, US20030088610, US20030093614, US20030097518, US20030105907, US20070162911, WO2003036450A2, WO2003036450A3, WO2003036482A2, WO2003036482A3, WO2003036485A2, WO2003036485A3, WO2003036508A2, WO2003036508A3, WO2003036884A2, WO2003036884A3, WO2003036902A2, WO2003036902A3|
|Publication number||10273718, 273718, US 2003/0084309 A1, US 2003/084309 A1, US 20030084309 A1, US 20030084309A1, US 2003084309 A1, US 2003084309A1, US-A1-20030084309, US-A1-2003084309, US2003/0084309A1, US2003/084309A1, US20030084309 A1, US20030084309A1, US2003084309 A1, US2003084309A1|
|Original Assignee||Sun Microsystems, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (5), Referenced by (40), Classifications (72), Legal Events (1)|
|External Links: USPTO, USPTO Assignment, Espacenet|
 This application claims priority from U.S. Provisional Patent Application No. 60/345,315 filed on Oct. 22, 2001 and entitled “High Performance Web Server,” which is incorporated herein by reference in its entirety for all purposes.
 1. Field of the Invention
 The present invention relates generally to microprocessors, and more particularly, to microprocessors that include a cryptographic co-processor within the microprocessor die.
 2. Description of the Related Art
 Server computers (i.e., servers) process all sorts of data transactions. One common type of data transaction is an encrypted data transaction that typically requires the server to perform at least one of an encryption function and a decryption function. FIG. 1 shows a typical server 102 and client computer 110 that are linked by a network 104, such as the Internet or other network.
FIG. 2 is a high-level block diagram of a typical server 102. As shown, the server 102 includes a processor 202, ROM 204, and RAM 206, each connected by a peripheral bus system 208. The peripheral bus system 208 may include one or more buses connected to each other through various bridges, controllers and/or adapters, such as are well known in the art. For example, the peripheral bus system 208 may include a “system bus” that is connected through an adapter to one or more expansion buses, such as a Peripheral Component Interconnect (PCI) bus. Also coupled to the peripheral bus system 208 are a mass storage device 210, a network interface 212, a number (N) of input/output (I/O) devices 216-1 through 216-N and a peripheral cryptographic processor 220.
 I/O devices 216-1 through 216-N may include, for example, a keyboard, a pointing device, a display device and/or other conventional I/O devices. Mass storage device 210 may include any suitable device for storing large volumes of data, such as a magnetic disk or tape, magneto-optical (MO) storage device, or any of various types of Digital Versatile Disk (DVD) or Compact Disk (CD) based storage.
 The peripheral cryptographic processor 220 (i.e., crypto-processor) is linked to the processor 202 by the peripheral bus system 208. The crypto-processor 220 performs encryption and decryption operations that may be necessary for encrypted data transactions such as between the server 102 and the client 110. In some servers the crypto-processor 220 can also be external to the server 102 and linked to the processor 202 by one of the I/O devices 216-1 through 216-N.
 Network interface 212 provides data communication between the computer system and other computer systems on the network 104. Hence, network interface 212 may be any device suitable for or enabling the server 102 to communicate data with a remote processing system (e.g., client computer 110) over a data communication link, such as a conventional telephone modem, an Integrated Services Digital Network (ISDN) adapter, a Digital Subscriber Line (DSL) adapter, a cable modem, a satellite transceiver, an Ethernet adapter, or the like.
 Typically the processor 202 can operate at clock speeds of up to or more than 1 GHz. Conversely, the peripheral bus system 208 typically operates at a substantially slower speed such as about 166 MHz or similar. Further, the crypto-processor 220 typically operates at a speed similar to the peripheral bus system 208. This is because the crypto-processor 220 cannot process data any faster than the data can be transported across the peripheral bus system 208. Further, the crypto-processor 220 is typically a customized, specialized processor (i.e. an application specific integrated circuit (ASIC)) that may not be made by the latest, highest performance manufacturing technologies and therefore the maximum processing speed (i.e., the crypto-processor clock speed) of the crypto-processor 220 is substantially less than the maximum processing speed of the processor 202.
FIG. 3 is a flowchart diagram of the method operations 300 of a typical encrypted data transaction within the server 102. The encrypted data transaction can be any data transaction that required encryption, decryption or both encryption and decryption such as an e-commerce transaction between the server 102 and the client computer 110. In operation 305, data is received in the server 102 such as from the client computer 110 or because of a request by the client computer 110.
 In operation 310, the received data is analyzed to determine if the received data is encrypted. For example, the data may be encrypted because the data includes a user's personal and/or financial data or other data that is transported during an encrypted session such as SSL (secure sockets layer) or other encryption methods.
 If the received data is found to not be encrypted data, in operation 310, then the received data is processed as described in operation 330 below. Alternatively, if, in operation 310, the received data is determined to be encrypted data, then, in operation 315, the encrypted data is sent to the peripheral crypto processor 220 via the peripheral bus system 208.
 In operation 320, the crypto processor 220 decrypts the encrypted data. In operation 325, the crypto processor 220 outputs the decrypted data to the processor 202 via the peripheral bus system 208. In operation 330, the processor 202 processes the data to produce result data.
 In operation 335, the result data is analyzed to determine if the result data should be encrypted. If the result data does not require encryption, then the processor outputs the result data to the client 110, in operation 340, and the method operations end. Alternatively, if, in operation 335, the result data required encryption, then in operation 345, the processor outputs the result data to the crypto-processor via the peripheral bus system 208.
 In operation 350, the crypto processor 220 encrypts the result data. In operation 355, the crypto processor 220 outputs the encrypted result data to the processor 202 via the peripheral bus system 208. In operation 360, the processor outputs the encrypted result data to the client 110 and the method operations end.
 Transferring the data to be encrypted, decrypted or processed between the crypto processor 220 and the processor 202 is very slow. Further, the slower processing speed of the crypto processor 220 also limits the rate at which the data is encrypted or decrypted. Further, if a large volume of data such as streaming data (e.g., streaming audio, streaming video, etc.) is being encrypted and/or decrypted then the rate the server 102 can serve the streaming data is limited by the rate at which the streaming data can be encrypted and/or decrypted. Further still, the multiple transfers of the streaming data between the crypto processor 220 and the processor 202 can dominate the usage of the peripheral bus system 208 and the I/O systems inside the crypto processor 220 and the processor 202, thereby limiting further the ability of the processor 202 to perform any functions other than transferring data to and from the crypto processor 220.
 In view of the foregoing, there is a need for a system and method for increased and/or more efficient data encryption and decryption process speeds.
 Broadly speaking, the present invention fills these needs by a system and method for increased and/or more efficient data encryption and decryption process speeds. It should be appreciated that the present invention can be implemented in numerous ways, including as a process, an apparatus, a system, computer readable media, or a device. Several inventive embodiments of the present invention are described below.
 One embodiment includes a microprocessor includes a first processing core, a first cryptographic co-processor and an integer multiplier unit that is coupled to the first processing core and the cryptographic co-processor. The first processing core includes an instruction decode unit, an instruction execution unit, a load/store unit. The first cryptographic co-processor is located on a first die with the first processing core. The cryptographic co-processor includes a cryptographic control register, a direct memory access engine that is coupled to the load/store unit in the first processing core and a cryptographic memory.
 The integer multiplier unit can be included within the first processing core or within the first cryptographic co-processor.
 The cryptographic memory is at least large enough to perform a Montgomery multiplication function.
 In one embodiment, the integer multiplier unit is a 64-bit×64-bit multiplier unit.
 The load/store unit can be coupled to a main memory system hierarchy.
 The first processing core is coupled to a second processing core by a processor crossbar. The second processing core is coupled to a second cryptographic coprocessor that is located on a second die with the second processing core. Alternatively, the second processing core and the second cryptographic co-processor can be located on the first die.
 The first cryptographic co-processor can be coupled to the instruction decoder unit.
 The first cryptographic co-processor and the first processing core share the integer multiplier unit.
 The direct memory access engine can be coupled to the load/store unit by a 64 bit data bus.
 The cryptographic control register can include data that identifies a type of cryptographic instruction received in the first cryptographic co-processor.
 One alternative embodiment includes a method of executing a cryptographic command. A cryptographic instruction is received in an load store unit in a processing core on a first die. The cryptographic instruction is analyzed to determine if the cryptographic instruction is a crypto store instruction. If the cryptographic instruction is a crypto store instruction, then a source operand of the crypto store instruction is stored in a crypto control register in a cryptographic co-processor on the first die. The source operand is analyzed to determine if the source operand identifies a corresponding crypto command. If the source operand identifies the corresponding crypto command, the corresponding crypto command is executed.
 The cryptographic co-processor can also send an interrupt to an instruction execution unit that is included in the processing core such as when execution of a crypto command is completed.
 A result of the cryptographic instruction can also be output to a memory system using a load store unit that is included in the processing core.
 Execution of the cryptographic instruction in the cryptographic co-processor can also include accessing data through the load store unit.
 The cryptographic co-processor can also include a direct memory access engine. Accessing data can also include loading and storing data in a main memory.
 Executing the cryptographic instruction in the cryptographic co-processor can also include executing a multiplication function. The cryptographic co-processor can include an integer multiplier unit for executing the multiplication function.
 The various embodiments of the present invention provide the ability for a crypto processor to rapidly encrypt and/or decrypt data, such as streaming data, at rates much greater than possible by a prior art crypto processor.
 Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
 The present invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, and like reference numerals designate like structural elements.
FIG. 1 shows a typical server and client computer that are linked by a network, such as the Internet or other network.
FIG. 2 is a high-level block diagram of a typical server.
FIG. 3 is a flowchart diagram of the method operations of a typical encrypted data transaction within the server.
FIG. 4 shows a single CPU die (chip) in accordance with one embodiment of the present invention.
FIG. 5 shows a detailed view of the processor core and cryptographic coprocessor in accordance with one embodiment of the present invention.
FIG. 6 is a flowchart 600 of the method operations of the paired processor 410 and crypto co-processor 420 according to one embodiment of the present invention.
 Several exemplary embodiments for a system and method for increased and/or more efficient data encryption and decryption process speeds will now be described. It will be apparent to those skilled in the art that the present invention may be practiced without some or all of the specific details set forth herein.
FIG. 4 shows a single CPU die (chip) 400 in accordance with one embodiment of the present invention. The CPU chip 400 includes a processing core 410. The processing core 410 is paired with a cryptographic co-processor 420. The cryptographic co-processor 420 is optimized to minimize the amount of hardware added to the CPU die 400. The CPU die 400 can also include additional processing cores 410 n and each of the additional processing cores 410 n is also paired with a cryptographic co-processor 420 n. The processing cores 410, 410 n are electrically coupled by a processor crossbar 430. The processor crossbar 430 is a data bus system that provides a common data communication link between the processing cores 410, 410 n and other common devices that may be accessed by the processing cores 410, 410 n such as memory systems and input/output (I/O) systems.
FIG. 5 shows a detailed view of the processor core 410 and cryptographic coprocessor 420 in accordance with one embodiment of the present invention. The processor core 410 includes an instruction decode/trap handler unit 504, an instruction execution unit 506, a load store unit 508 and an integer multiplier unit 514. An instruction cache 502 is coupled to the input of the instruction decode/trap handler unit 504. A data cache 520 is coupled to the load store unit 508. The data cache 520 and the instruction cache 502 are also coupled to the processor crossbar 430. The data cache 520 can be a level-1 cache and can be between about 4 kb and about 64 kb in size.
 The crypto-coprocessor 420 includes a crypto control register 510, a crypto memory 516, a DMA engine 518 and the crypto co-processor core 512. The crypto control register 510 stores the settings of the crypto co-processor 420. The settings can include identifying the type of encryption or decryption command or operation to be performed. The types of encryption or decryption command can include any of the encryption and decryption schemes known in the art. The crypto control register 510 also stores the status of the current crypto operations and is accessible by the processor 410 so that the processor 410 can check the status of the current crypto operations. The crypto control register 510 is linked to the load store unit 508 by a logical link 530, which represents the bi-directional interchange of data between the load store unit 508 and the crypto control register 510.
 The DMA engine 518 is coupled to the load store unit 508 by a crypto bus 522. The DMA engine 518 provides more direct access to the memory system hierarchy, such as the main memory, the data cache 520 and a level-2 cache, that can be accessed via the load store unit 508 and, if necessary, the processor crossbar 430. The crypto bus 522 can be as wide as feasible to enable rapid data transfer between the crypto coprocessor 420 and the processing core 410. In one embodiment, the crypto bus 522 is a 64-bit bus.
 The crypto memory 516 is sufficiently large enough to hold the operands and results for a particular crypto operation. By way of example, in an RSA decryption application, the crypto memory 516 is about 1.3 KB, which is large enough for a modular exponentiation on 2048-bit keys.
 As shown in FIG. 5, the integer multiplier unit 514 is included within the crypto processor core 512 but directly accessible by the processor core 410 by a logical link 532. Alternatively, the integer multiplier unit 514 can be part of the processor core 410 as long as the crypto processor core 512 can directly access the integer multiplier unit 514. In this manner the crypto processor core 512 and the processor core 410 can share the integer multiplier unit 514 so as to reduce the space used (i.e., number of devices required) on the die. Typical, prior art crypto processors were not included on the die 400 with the processor core because the crypto processors consumed too much valuable space on the die that was needed more for the processor core.
 Sharing several components significantly reduces the “footprint” of the crypto processor so as to allow the crypto processor to be placed on the same die 400 as the processor core. The integer multiplier unit 514 performs the modular multiply and modular exponentiation functions. The processor core 410 only uses the integer multiplier unit 514 about 2-5% of the time. Therefore the crypto processor 420 can use the integer multiplier 514 about 95-98% of the time without impacting operations within the processor core 410. Moving the integer multiplier unit 514 into the crypto processor 420 further streamlines the crypto functions of the integer multiplier unit 514.
 The integer multiplier unit 514 is capable of performing modular arithmetic such as Montgomery multiply functions and exponentiation. A Montgomery multiply function is a technique for performing modular multiplication on a large integer (e.g. a 2048 bit number) using two multiplications rather than a multiplication and a division. The integer multiplier unit 514 can be a 64-bit×64-bit integer multiplier unit. A 64 bit×64-bit integer multiplication unit can directly access operands that are stored in the crypto memory 516 rather than flooding the crypto bus 522 and the load store unit 508 every clock cycle. Flooding the crypto bus 522 and the load store unit 508 every clock cycle would effectively stall the processor core 410 because the load store unit 508 would only be able to address the demands of the crypto processor 420. Having a crypto memory 516 that is sufficiently large enough to perform a complete modular exponentiation relieves the data throughput load on the crypto bus 522 and the load store unit 508 and thereby allows the processor core 410 and the crypto processor 420 to operate in simultaneously on different operations and functions for many clock cycles.
FIG. 6 is a flowchart 600 of the method operations of the paired processor 410 and crypto co-processor 420 according to one embodiment of the present invention. The instruction cache 502 temporarily stores the next instruction to be executed in the processor core 410. In operation 605 the next instruction is received in the instruction decode/trap handler unit 504 from the instruction cache 502.
 The received instruction is forwarded to the instruction execution unit 506 for execution in operation 610. The instruction execution unit 506 analyzes the received instruction to determine if the received instruction is a load or a store instruction in operation 615.
 If, in operation 615 above, the received instruction is not a load or store instruction, the instruction is executed as required in the various stages 504, 506, 508 of the processor core 410 as necessary to complete execution of the non-load/non-store instruction, in operation 620 and the method operations on the executed instruction result ends.
 If, in operation 615 above, the received instruction is a load instruction or a store instruction, the received instruction is forwarded to the load store unit 508 in operation 630.
 In operation 635, the load store unit 508 analyzes the received instruction to determine if the received instruction is a crypto load instruction or a crypto store instruction.
 If, in operation 635, the received instruction is not a crypto load instruction or a crypto store instruction, the non-crypto store instruction/non-crypto load instruction is executed in the load store unit 508 (i.e., the prescribed load or store function is performed) in operation 640 and the method operations for that instruction ends.
 If, in operation 635, the received instruction is a crypto load instruction or a crypto store instruction, the crypto load or crypto store instruction is analyzed in operation 650.
 If, in operation 650, the crypto load or crypto store instruction is a crypto load instruction, the load/store unit 508 transfers the data from the crypto co-processor 420 back to the processor 410, in operation 655 and the method operations for the instruction end.
 If, in operation 650, the crypto load or crypto store instruction is a crypto store instruction (i.e., not a crypto load instruction), the load/store unit 508 transfers a source operand of the crypto store instruction to the crypto control register 510 in operation 660. In operation, 665, the crypto co-processor 420 analyzes the data in the crypto control registers 510 to determine if the stored data identifies a corresponding crypto command. If the data does not identify a corresponding crypto command, the method operations for the instruction end.
 If, in operation 665, the data identifies a corresponding crypto command, the corresponding crypto command is executed in operation 670.
 When the execution of the crypto command is complete, the crypto coprocessor 420 can send an interrupt to the instruction execution unit 506 in the processor core 410 via the logical link 534, in operation 670 and the method operations for the crypto command ends. Some crypto command can also cause data in the crypto memory 516 to be output to the memory system via the load store unit 508. Conversely, some crypto commands will cause data in the memory system to be loaded into the crypto memory via the load store unit 508.
 The crypto co-processor 420 can process data independent of the processor core 410 for multiple and even thousands of clock cycles. Pairing the crypto processor 420 with the processing core 410 on the same die 400 increases the speed of the encryption and/or decryption processes by operating the crypto processor 420 and the processing core 410 at the same clock speed. The speed of the encryption and/or decryption processes is also increased because the data (e.g., data stream) to be encrypted and/or decrypted is not required to be transmitted the relatively long distance between the crypto processor 220 and the processor 202, at the much slower speed across the peripheral bus 208 such as described in FIG. 2 above. Further, the pairing the crypto processor 420 with the processing core 410 allows the crypto processor 420 to directly access the memory system hierarchy through the crypto processor's 420 DMA engine 518 and the load store unit 508. This direct memory access allows the crypto processor 420 to rapidly encrypt and/or decrypt streaming data at rates much greater than possible by a peripheral crypto processor 220 shown in FIG. 2 above.
 As used herein the term “about” means +/−10%. By way of example, the phrase “about 250” indicates a range of between 225 and 275.
 With the above embodiments in mind, it should be understood that the invention might employ various computer-implemented operations involving data stored in computer systems. These operations are those requiring physical manipulation of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. Further, the manipulations performed are often referred to in terms, such as producing, identifying, determining, or comparing.
 It will be further appreciated that the instructions represented by the operations in FIG. 6 are not required to be performed in the order illustrated, and that all the processing represented by the operations may not be necessary to practice the invention.
 Although the foregoing invention has been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. Accordingly, the present embodiments are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US2151733||4 May 1936||28 Mar 1939||American Box Board Co||Container|
|CH283612A *||Title not available|
|FR1392029A *||Title not available|
|FR2166276A1 *||Title not available|
|GB533718A||Title not available|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7392399 *||5 May 2003||24 Jun 2008||Sun Microsystems, Inc.||Methods and systems for efficiently integrating a cryptographic co-processor|
|US7400722 *||24 Dec 2002||15 Jul 2008||Broadcom Corporation||Methods and apparatus for performing hash operations in a cryptography accelerator|
|US7434043||23 Jan 2003||7 Oct 2008||Broadcom Corporation||Cryptography accelerator data routing unit|
|US7568110 *||23 Jan 2003||28 Jul 2009||Broadcom Corporation||Cryptography accelerator interface decoupling from cryptography processing cores|
|US7600131||6 Jul 2000||6 Oct 2009||Broadcom Corporation||Distributed processing in a cryptography acceleration chip|
|US7664810 *||16 May 2005||16 Feb 2010||Via Technologies, Inc.||Microprocessor apparatus and method for modular exponentiation|
|US7669086||2 Aug 2006||23 Feb 2010||International Business Machines Corporation||Systems and methods for providing collision detection in a memory system|
|US7685392||28 Nov 2005||23 Mar 2010||International Business Machines Corporation||Providing indeterminate read data latency in a memory system|
|US7721140||2 Jan 2007||18 May 2010||International Business Machines Corporation||Systems and methods for improving serviceability of a memory system|
|US7725624 *||30 Dec 2005||25 May 2010||Intel Corporation||System and method for cryptography processing units and multiplier|
|US7765368||5 Jul 2007||27 Jul 2010||International Business Machines Corporation||System, method and storage medium for providing a serialized memory interface with a bus repeater|
|US7844771||31 Mar 2008||30 Nov 2010||International Business Machines Corporation||System, method and storage medium for a memory subsystem command interface|
|US7870459||23 Oct 2006||11 Jan 2011||International Business Machines Corporation||High density high reliability memory module with power gating and a fault tolerant address and command bus|
|US7900022 *||14 Feb 2006||1 Mar 2011||Intel Corporation||Programmable processing unit with an input buffer and output buffer configured to exclusively exchange data with either a shared memory logic or a multiplier based upon a mode instruction|
|US7920701||14 Dec 2005||5 Apr 2011||Nvidia Corporation||System and method for digital content protection|
|US7934115||11 Dec 2008||26 Apr 2011||International Business Machines Corporation||Deriving clocks in a memory system|
|US7996670||6 Jul 2000||9 Aug 2011||Broadcom Corporation||Classification engine in a cryptography acceleration chip|
|US8028164 *||19 Mar 2004||27 Sep 2011||Nokia Corporation||Practical and secure storage encryption|
|US8312292 *||31 Jul 2008||13 Nov 2012||Viasat, Inc.||Input output access controller|
|US8315381||1 Jul 2008||20 Nov 2012||Broadcom Corporation||Methods and apparatus performing hash operations in a cryptography accelerator|
|US8356361 *||21 Dec 2006||15 Jan 2013||Spansion Llc||Secure co-processing memory controller integrated into an embedded memory subsystem|
|US8392983||31 Jul 2008||5 Mar 2013||Viasat, Inc.||Trusted labeler|
|US8473750||14 Dec 2005||25 Jun 2013||Nvidia Corporation||Chipset security offload engine|
|US8549260 *||29 Jan 2009||1 Oct 2013||Infineon Technologies Ag||Apparatus for processing data and method for generating manipulated and re-manipulated configuration data for processor|
|US8681973 *||15 Sep 2010||25 Mar 2014||At&T Intellectual Property I, L.P.||Methods, systems, and computer program products for performing homomorphic encryption and decryption on individual operations|
|US8756605||17 Dec 2004||17 Jun 2014||Oracle America, Inc.||Method and apparatus for scheduling multiple threads for execution in a shared microprocessor pipeline|
|US8891757 *||17 Feb 2012||18 Nov 2014||Bull Sas||Programmable cryptographic integrated circuit|
|US8918650 *||27 Oct 2008||23 Dec 2014||Sandisk Il Ltd.||Secure data processing for unaligned data|
|US20040123119 *||23 Jan 2003||24 Jun 2004||Broadcom Corporation||Cryptography accelerator interface decoupling from cryptography processing cores|
|US20040123120 *||23 Jan 2003||24 Jun 2004||Broadcom Corporation||Cryptography accelerator input interface data handling|
|US20040123123 *||24 Sep 2003||24 Jun 2004||Buer Mark L.||Methods and apparatus for accessing security association information in a cryptography accelerator|
|US20040225885 *||5 May 2003||11 Nov 2004||Sun Microsystems, Inc||Methods and systems for efficiently integrating a cryptographic co-processor|
|US20040230813 *||12 May 2003||18 Nov 2004||International Business Machines Corporation||Cryptographic coprocessor on a general purpose microprocessor|
|US20050210280 *||19 Mar 2004||22 Sep 2005||Nokia Corporation||Practical and secure storage encryption|
|US20050256920 *||16 May 2005||17 Nov 2005||Crispin Thomas A||Microprocessor apparatus and method for modular exponentiation|
|US20080109903 *||21 Dec 2006||8 May 2008||Spansion Llc||Secure co-processing memory controller integrated into an embedded memory subsystem|
|US20100318811 *||16 Dec 2010||Kabushiki Kaisha Toshiba||Cryptographic processor|
|US20120066510 *||15 Sep 2010||15 Mar 2012||At&T Intellectual Property I, L.P.||Methods, systems, and computer program products for performing homomorphic encryption and decryption on individual operations|
|US20120213360 *||23 Aug 2012||Bull Sas||Programmable cryptographic integrated circuit|
|EP1801725A2 *||14 Dec 2006||27 Jun 2007||Nvidia Corporation||Chipset security offload engine|
|U.S. Classification||713/189, 712/E09.067, 712/E09.032|
|International Classification||G06F15/167, G06F13/38, G06F1/32, G06F15/173, G06F12/00, G06F13/14, G11C11/4074, H04L12/56, G06F12/16, G06F13/00, G06F15/16, G06F9/46, G06F13/16, G06F11/10, G06F12/08, G09C1/00, H04L29/06, G06F9/30, G06F9/38, G06F21/00, G06F15/78|
|Cooperative Classification||Y02B60/1228, G06F1/3203, H04L49/90, H04L47/10, Y02B60/1225, G06F9/30043, G06F12/084, G06F1/3225, H04L45/745, G06F9/3879, H04L49/9057, G06F12/0813, G06F21/72, H04L29/06, G06F1/3275, H04L49/9089, G06F9/3891, G06F12/0811, G06F9/3851, H04L47/2441, G06F11/108, G11C11/4074, G06F13/1689, H04L69/22|
|European Classification||G06F9/30A2L, G06F9/38S1, G06F9/38E4, H04L47/10, G06F12/08B4L, G06F11/10M, G06F21/72, H04L49/90R1, G06F12/08B4N, G06F1/32P5P8, G06F12/08B4S, H04L49/90, H04L49/90P, H04L29/06, G06F1/32P, G06F1/32P1C6, G11C11/4074, G06F9/38T6C, G06F15/173N4A, H04L47/24D, H04L45/745, G06F13/16D8, G06F11/10R1, G06F15/78P1C|
|18 Oct 2002||AS||Assignment|
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KOHN, LESLIE D.;REEL/FRAME:013405/0185
Effective date: 20021017