Write, autoreview, editor, reviewer
3,129
edits
Measurement-Only Universal Blind Quantum Computation: Difference between revisions
Measurement-Only Universal Blind Quantum Computation (edit)
Revision as of 09:59, 6 June 2019
, 6 June 2019→Protocol 1a: Device Independent
m (→Outline) |
|||
| Line 13: | Line 13: | ||
The following Universal Blind Quantum Computation (UBQC) protocol uses the unique feature of [[Supplementary Information#Measurement Based Quantum Computation|Measurement Based Quantum Computation (MBQC)]] that separates the classical and quantum parts of a computation. Based on its counterpart Prepare and Send UBQC, this protocol requires Client to possess only a measurement device in order to perform blind quantum computation, hence the name 'Measurement Only UBQC'. The motivation behind this protocol lies in the fact that for several experimental setups like optical systems, measurement of a state is much easier than the generation of a state. Presented below are two versions of the protocol. The first protocol needs only quantum communication throughout the protocol while the second needs both quantum and classical throughout the communication. These protocols are designed for classical input and output. It can be extended to quantum input/output by modifying the measurement angles of the Client according to Prepare and Send UBQC in order to hide her quantum output from the Server. Like all the other delegated quantum computing protocols, this protocol is also divided into two stages, Preparation and Computation. | The following Universal Blind Quantum Computation (UBQC) protocol uses the unique feature of [[Supplementary Information#Measurement Based Quantum Computation|Measurement Based Quantum Computation (MBQC)]] that separates the classical and quantum parts of a computation. Based on its counterpart Prepare and Send UBQC, this protocol requires Client to possess only a measurement device in order to perform blind quantum computation, hence the name 'Measurement Only UBQC'. The motivation behind this protocol lies in the fact that for several experimental setups like optical systems, measurement of a state is much easier than the generation of a state. Presented below are two versions of the protocol. The first protocol needs only quantum communication throughout the protocol while the second needs both quantum and classical throughout the communication. These protocols are designed for classical input and output. It can be extended to quantum input/output by modifying the measurement angles of the Client according to Prepare and Send UBQC in order to hide her quantum output from the Server. Like all the other delegated quantum computing protocols, this protocol is also divided into two stages, Preparation and Computation. | ||
===Protocol 1a: Device Independent=== | ===Protocol 1a: Device Independent=== | ||
*''Server’s preparation'' Server prepares the resource graph state required for MBQC by the Client. | *''Server’s preparation'': Server prepares the resource graph state required for MBQC by the Client. | ||
*'' Interaction and Client’s Computation'' Server sends single qubits of the prepared resource state to the Client who measures it in the basis required to carry out the quantum computation according to the measurement pattern in her mind. She records the outcomes and at the end of computation stage, gets the result of her computation. This protocol is not tolerant to channel losses. | *'' Interaction and Client’s Computation'': Server sends single qubits of the prepared resource state to the Client who measures it in the basis required to carry out the quantum computation according to the measurement pattern in her mind. She records the outcomes and at the end of the computation stage, gets the result of her computation. This protocol is not tolerant to channel losses. | ||
===Protocol 1b: Tolerant to high channel losses=== | ===Protocol 1b: Tolerant to high channel losses=== | ||
*''Server’s preparation'' This step remains the same as protocol 1a | *''Server’s preparation'' This step remains the same as protocol 1a | ||