Editing Measurement-Only Universal Blind Quantum Computation
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
The [https://journals.aps.org/pra/abstract/10.1103/PhysRevA.87.050301 example protocol] achieves the functionality of [[Secure Client- Server Delegated Computation]] by assigning quantum computation to an untrusted device while maintaining privacy of the input, output and computation of the client. The client requires to be able to prepare and send quantum states while the server requires to possess a device with quantum memory, measurement and entanglement generation technology. Following description deals with a method which involves quantum online and classical online communication, called Blind Quantum Computation. It means the protocol needs continuous quantum | The [https://journals.aps.org/pra/abstract/10.1103/PhysRevA.87.050301 example protocol] achieves the functionality of [[Secure Client- Server Delegated Computation]] by assigning quantum computation to an untrusted device while maintaining privacy of the input, output and computation of the client. The client requires to be able to prepare and send quantum states while the server requires to possess a device with quantum memory, measurement and entanglement generation technology. Following description deals with a method which involves quantum online and classical online communication, called Blind Quantum Computation. It means the protocol needs continuous quantum ad classical communication between the parties, throughout the execution. It comes with the properties of [[Secure Client- Server Delegated Quantum Computation#Properties|correctness]], [[Secure Client- Server Delegated Quantum Computation#Properties|blindness]] and [[Secure Client- Server Delegated Quantum Computation#Properties|universality]].</br></br> | ||
'''Tags:''' [[Category: Two Party Protocols]] [[:Category: Two Party Protocols|Two Party]], [[Category: Universal Task]][[:Category: Universal Task|Universal Task]], [[Category: Quantum Functionality]] [[:Category: Quantum Functionality|Quantum Functionality]], Quantum Online communication, Classical Online communication, [[Supplementary Information#Measurement Based Quantum Computation|Measurement Based Quantum Computation (MBQC)]], | '''Tags:''' [[Category: Two Party Protocols]] [[:Category: Two Party Protocols|Two Party]], [[Category: Universal Task]][[:Category: Universal Task|Universal Task]], [[Category: Quantum Functionality]] [[:Category: Quantum Functionality|Quantum Functionality]], Quantum Online communication, Classical Online communication, [[Supplementary Information#Measurement Based Quantum Computation|Measurement Based Quantum Computation (MBQC)]], | ||
[[Prepare and Send-Universal Blind Quantum Computation|Prepare and Send-UBQC]], [[Measurement-Only Verifiable Universal Blind Quantum Computation|Measurement Only Verifiable UBQC]], [[Quantum Key Distribution|QKD]], [[Quantum Teleportation]]. | [[Prepare and Send-Universal Blind Quantum Computation|Prepare and Send-UBQC]], [[Measurement-Only Verifiable Universal Blind Quantum Computation|Measurement Only Verifiable UBQC]], [[Quantum Key Distribution|QKD]], [[Quantum Teleportation]]. | ||
Line 32: | Line 32: | ||
*Server should be able to generate and store large network of entangled quantum states. | *Server should be able to generate and store large network of entangled quantum states. | ||
[[File:Measurement-Only Universal Blind Quantum Computation.png|center|Measurement-Only Universal Blind Quantum Computation]] | |||
==Properties== | ==Properties== | ||
Line 49: | Line 47: | ||
==Notations== | ==Notations== | ||
*(m,n,o) dimensions of cluster state. It could be 2D or 3D. | *(m,n,o) dimensions of cluster state. It could be 2D or 3D. | ||
== | ==Pseudocode== | ||
*Unless given specific mention in [.], following steps apply to both protocols | *Unless given specific mention in [.], following steps apply to both protocols | ||
*'''Input:''' Server: Dimensions of Resource State (m,n,o) | *'''Input:''' Server: Dimensions of Resource State (m,n,o) | ||
Line 68: | Line 60: | ||
###Client measures <math>|\psi\rangle_{i,j,k}\rangle</math> in the required measurement basis according to her measurement pattern | ###Client measures <math>|\psi\rangle_{i,j,k}\rangle</math> in the required measurement basis according to her measurement pattern | ||
##[Protocol 1b] | ##[Protocol 1b] | ||
###Server creates <math>\ | ###Server creates [[Glossary#Bell States|Bell pair]] <math>\phi_{1,2}=\frac{1}{\sqrt{2}}(|00\rangle+|11\rangle)</math> | ||
###Server sends to Client (<math>|\phi_2\rangle</math>) and waits for Client's response | ###Server sends to Client (<math>|\phi_2\rangle</math>) and waits for Client's response | ||
###Client checks if she received and tells the Server as Client.Response() | ###Client checks if she received and tells the Server as Client.Response() | ||
###'''If Client.Response()=No''', Server repeats the previous two steps | ###'''If Client.Response()=No''', Server repeats the previous two steps | ||
###'''Else''' Client measures (<math>|\phi_2\rangle</math>) in measurement basis {<math>|0\rangle \pm e^{i\theta}|1\rangle</math> | ###'''Else''' Client measures (<math>|\phi_2\rangle</math>) in measurement basis {<math>|0\rangle \pm e^{i\theta}|1\rangle</math> determined by measurement pattern. | ||
###'''Server's Computation: [[Glossary#Gate Teleportation|Gate Teleportation]]''' | ###'''Server's Computation: [[Glossary#Gate Teleportation|Gate Teleportation]]''' | ||
####He entangles <math>|\phi_2\rangle</math> with <math>|\psi\rangle_{i,j,k}</math> by performing [[Glossary# | ####He entangles <math>|\phi_2\rangle</math> with <math>|\psi\rangle_{i,j,k}</math> by performing [[Glossary#Quantum Gates|C-Z]] | ||
####He measures <math>|\psi\rangle_{i,j,k}</math> in X basis ({<math>|+\rangle,|-\rangle</math>}) | ####He measures <math>|\psi\rangle_{i,j,k}</math> in X basis ({<math>|+\rangle,|-\rangle</math>}) | ||
####Server's applies correction on the classical outcome using Gate Teleporation | ####Server's applies correction on the classical outcome using Gate Teleporation. | ||
###Server communicates the corrected outcome | ###Server communicates the corrected outcome. | ||
####Client records Server’s outcome and uses it when computing the final result or measurement angles for further qubits | ####Client records Server’s outcome and uses it when computing the final result or measurement angles for further qubits. | ||
*Interaction and Computation steps are repeated until all the qubits of resource state are measured. | *Interaction and Computation steps are repeated until all the qubits of resource state are measured. | ||
<div style='text-align: right;'>''*contributed by Shraddha Singh''</div> | <div style='text-align: right;'>''*contributed by Shraddha Singh''</div> |