Write, autoreview, editor, reviewer
3,129
edits
Secure Client- Server Delegated Computation: Difference between revisions
Secure Client- Server Delegated Computation (view source)
Revision as of 12:17, 8 October 2018
, 8 October 2018→Classical Offline Communication-No Quantum Communication
| Line 15: | Line 15: | ||
===Classical Offline Communication-No Quantum Communication=== | ===Classical Offline Communication-No Quantum Communication=== | ||
It involves a fully classical Client assign quantum computation to a Server on her classical input/output using only classical communication during the preparation stage and output correction. There is no communication between the two parties during computation stage. It uses only classical [[Supplementary Information#Homomorphic Encryption| | It involves a fully classical Client assign quantum computation to a Server on her classical input/output using only classical communication during the preparation stage and output correction. There is no communication between the two parties during computation stage. It uses only classical [[Supplementary Information#Homomorphic Encryption|Homomorphic Encryption]] and no quantum gadgets to realize a quantum functionality. Quantum offline communication would be needed in case of quantum input/output. Protocols falling under this category are quantum capable Classical Fully Homomorphic Encryption [[Classical Fully Homomorphic Encryption for Quantum Circuits|'''(FHE) for Quantum Circuits''']]. A verification of FHE for Quantum Circuits protocol is still an open question. | ||
== Use Case == | == Use Case == | ||