Secure Multiparty Delegated Quantum Computation
Jump to navigation
Jump to search
This example protocol achieves the functionality of Delegation Quantum Computation to a server for multiple Clients with the guarantee that Server is unknown of any Clients' inputs, outputs, and computation. This protocol is an extension of Prepare-and-Send Universal Blind Quantum Computation in the multiparty setting.
Tags: Multi Party Protocols, Quantum Functionality, Universal Task
Assumptions
- The clients have secure access to classical multiparty functionalities, which will be treated as oracles.
- A set of malicious clients cannot corrupt the Server, and the other way around.
Outline
The Protocol consists of 2 phases: Preparation phase and Computation phase.
Preparation phase
- Input qubits: For the input qubit states, each client one-time pads their qubit and uses secret sharing schemes to share the secret values with other clients. The honest behaviour for every client is enforced via the given protocol. The server then one-time pads them and measures the one-time padded qubits and announces the measurement values.
- Non-output and non-input qubits: The clients send the qubits in random phases allowed in MBQC. The server then one-time pads them and announces the measurement values.
- Output qubits: The server prepares them in the state.
- Graph state: The server entangles the qubits to a brickwork state.
Computation phase
- Non-output qubits: All clients choose a random bit based on which they compute the measurement angle of the qubits. They send this angle to the server who then returns the result based on the measurement.
- Output qubits: The server sends the encrypted qubits to the corresponding clients. The clients then jointly compute the Pauli corrections and apply them to get the actual output.
Notation
- : Total clients.
- : Client with index .
- : Register of client .
- : Server performing the computation.
- : Set of input qubits.
- : Set of output qubits.
- : Set of all qubits except the output qubits.
- : Register of server with register index .
- : Outcome of the measurement for the qubit corresponding to client for qubit.
- : Random bit chosen by client in preparation phase.
- : Random bit chosen by client for qubit in computation phase.
- : Random phase given by client to qubit.
- : Measurement angle for encrypted qubit .
- : Measurementangle for decrypted qubit.
- : correction term for qubit.
- : correction term for qubit.
Requirements
- The quantum operations required from the clients are limited to creating states and applying X gates and rotations around the z-axis.
Knowledge Graph
Properties
- There is no need of quantum memory for the clients as the quantum communication from the clients to the server can be done in single-qubit rounds.
- The protocol provides security against a dishonest Server and against a coalition of dishonest clients.
- Security in the more general scenario where a Server and some clients collaborate to cheat is not guaranteed.
- No guarantee is given on the correctness of the computation outcome.
- The protocol uses Verifiable Secret Sharing (VSS) schemes and a computation oracle to calculate the necessary values at each step of the protocol and to ensure that the clients behave honestly.
Protocol Description
- Enforcing honest behavior for client
- Client sends qubits to the Server and secret-shares the values with all clients, using a VSS scheme.
- The Server requests the shared values from the clients for all but one qubit, and measures in the resconstructed bases. If the bases agree with the results of the measurements, then with high probability, the remaining state is correctly formed in relation to the shared angle.
- State preparation for )
- Server stores states received from clients to distinct registers ();
- for
- if then break;
- if and then break;
- if , then
- CNOT on ;
- else
- CNOT on ;
- measure state in and get outcome ;
- if then
- CNOT on ;
- Measure state in and get outcome ;
- CNOT on ;
- else
- CNOT on ;
- Measure state in and get outcome ;
- CNOT on ;
- for
\begin{figure}[H]
\centerline{ \Qcircuit @C=0.5em @R=1.5em { \lstick{C_1:20:28, 17 April 2019 (CEST)20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^1}}} &\qw &\targ &\meter & \cw & t_j^1\\ \lstick{C_2:20:28, 17 April 2019 (CEST)20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^2}}} &\qw &\ctrl{-1}&\qw &\targ & \meter & \cw & t_j^2\\ \lstick{C_3:20:28, 17 April 2019 (CEST)20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^3}}} &\qw &\qw &\qw &\ctrl{-1} &\qw &\targ{+1} & \meter & \cw & \cw &Shraddha (talk) 20:28, 17 April 2019 (CEST) t_j^3\\ \lstick{\vdots \hspace{1in}\vdots} & & & & & & \vdots & & & & & & & & & & \ddots \\ \lstick{C_n:20:28, 17 April 2019 (CEST)20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^n}}} &\qw &\qw &\qw & \qw &\qw &\qw &\qw &\qw & \qw &\qw &\qw &\qw & \qw &\ctrl{-1} &\qw &\targ & \meter & \cw & \cw &20:28, 17 April 2019 (CEST)~ t_j^n\\ \lstick{C_j:~X^{a_j}Z(\theta_j^j)\big[\mathcal{C}_j\big] } Shraddha (talk) 20:28, 17 April 2019 (CEST) &\qw &\qw &\qw & \qw &\qw &\qw &\qw &\qw & \qw &\qw &\qw & \qw & \qw & \qw &\qw & \ctrl{-1} &\qw & \qw & & &\hspace{0.7in}X^{a_j}Z(\theta_j)\big[\mathcal{C}_j\big] \\\\ } } \caption{Remote State Preparation with quantum input (Protocol \ref{Algo2}). Client </math>C_j</math> performs a one-time pad on his register </math>\mathcal{C}_j</math> and the result of the circuit remains one-time padded, where </math>\theta_j=\theta_j^j+\sum_{k=1,k\neq j}^n (-1)^{\bigoplus_{i=k}^n t_j^i+a_j}\theta_j^k</math>.}\label{fig:algo1}
\end{figure}
State preparation for ()
- Server stores states received from clients to distinct registers ();
- For
- CNOT on ;
- Measure state in and get outcome ;
\begin{figure}[H]
\centerline{ \Qcircuit @C=0.5em @R=1.5em { \lstick{C_1:Shraddha (talk) 20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^1}}} &\qw &\targ &\meter & \cw & t_j^1\\ \lstick{C_2:Shraddha (talk) 20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^2}}} &\qw &\ctrl{-1}&\qw &\targ & \meter & \cw & t_j^2\\ \lstick{C_3:Shraddha (talk) 20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^3}}} &\qw &\qw &\qw &\ctrl{-1} &\qw &\targ & \meter & \cw & \cw &Shraddha (talk) 20:28, 17 April 2019 (CEST) t_j^3\\ \lstick{\vdots \hspace{0.7in}\vdots} \hspace{0.5in} & & & & & & \vdots & & & & & & & & & & \ddots \\ \lstick{C_{n-1}:\hspace{0.1in}\ket{+_{\theta_j^{n-1}}}} &\qw &\qw &\qw & \qw &\qw &\qw &\qw &\qw & \qw &\qw &\qw &\qw & \qw &\ctrl{-1} &\qw &\targ & \meter & \cw & \cw & 20:28, 17 April 2019 (CEST) t_j^{n-1}\\ \lstick{C_n:Shraddha (talk) 20:28, 17 April 2019 (CEST)\ket{+_{\theta_j^n}}} &\qw &\qw &\qw & \qw &\qw &\qw &\qw &\qw & \qw &\qw &\qw & \qw & \qw & \qw &\qw & \ctrl{-1} &\qw & \qw & & &\hspace{0.3in}\mathbf{\ket{+_{\theta_j}}}\\ } } \caption{Remote State Preparation without quantum input (Protocol \ref{Algo3}), where </math>\theta_j=\theta_j^n+\sum_{k=1}^{n-1} (-1)^{\bigoplus_{i=k}^{n-1} t_j^i}\theta_j^k</math>.}\label{fig:algo2}
\end{figure}
Multiparty Quantum Computing Protocol
- A quantum input and measurement angles for qubits .
Preparation phase
Quantum input: For
- Client applies a one-time pad to his qubit, where and and sends it to the Server. He secret-shares the values and with the other clients.
- Each client , runs Protocol 1 with the Server. If all clients pass the test, the Server at the end has states for .
- The Server runs Protocol2 and announces outcome vector .
At this point the Server has the state , where
- [non-output / non-input qubits:] For
\begin{enumerate} \item[4.] All clients </math>C_k</math>, </math>k\in[n]</math> run Protocol \ref{Algo1} with the Server. If all clients pass the test, the Server at the end has </math>n</math> states </math>\ket{+_{\theta_j^k}}=\frac{1}{\sqrt{2}}\big(\ket{0}+e^{i\theta_j^k}\ket{1} \big)</math> for </math>k=1,\dots,n</math>. \item[5.] The Server runs Protocol \ref{Algo3} getting outcome vector </math>\mathbf{t}_j</math>. He ends up with the state </math>\ket{+_{\theta_j}}</math>, where: \begin{equation}\label{eq:entangle2} \theta_j=\theta_j^n+\sum_{k=1}^{n-1} (-1)^{\bigoplus_{i=k}^{n-1} t_j^i}\theta_j^k \end{equation} \end{enumerate} \item[output qubits:] For </math>j\in O</math>, the Server prepares </math>\ket{+}</math> states. \item[graph state:] The Server entangles the </math>n+q</math> qubits to a brickwork state by applying ctrl-</math>Z</math> gates. \end{description} \begin{flushleft} \underline{\emph{Computation phase}} \vspace{-7pt} \end{flushleft} \begin{description} \item[non-output qubits:] For </math>j\in O^c</math> \begin{enumerate} \item All clients </math>C_k</math>, </math>k=1,\dots,n</math> choose random </math>r_j^k\in\{0,1\}</math>, which they secret-share with the other clients. Then using a computation oracle, they compute the measurement angle of qubit </math>j</math>: \begin{equation}\label{angle} \delta_j:=\phi'_j+\pi r_j+\theta_j \end{equation} where undefined values are equal to zero, or otherwise: \begin{itemize} \item </math>\phi'_j=(-1)^{a_j+s_j^X}\phi_j+s^Z_j\pi+a_{f^{-1}(j)}\pi</math>. \item </math>r_j=\bigoplus\limits_{k=1}^n r_j^k</math>. \item </math>s_i=b_i\oplus r_i</math>, for </math>i\leq j</math>. \end{itemize} \item The Server receives </math>\delta_j</math> and measures qubit </math>j</math> in basis </math>\{\ket{+_{\delta_j}},\ket{-_{\delta_j}}\}</math>, getting result </math>b_j</math>. He announces </math>b_j</math> to the clients. \end{enumerate} \item[output qubits:] For </math>j\in O</math>, the Server sends the ``encrypted quantum state to client </math>C_{j-q}</math>. All participants jointly compute </math>s_j^X</math> and </math>s_j^Z</math> and send it to client </math>C_{j-q}</math>, who applies operation </math>Z^{s_j^Z}X^{s_j^X}</math> to retrieve the actual quantum output. \end{description}
\end{algorithm}
*contributed by Natansh Mathur