Device-Independent Quantum Key Distribution: Difference between revisions

From Quantum Protocol Zoo
Jump to navigation Jump to search
Line 6: Line 6:
* '''Network:''' we assume the existence of an authenticated public classical channel between Alice and Bob.
* '''Network:''' we assume the existence of an authenticated public classical channel between Alice and Bob.
* '''Timing:''' we assume that the network is synchronous.
* '''Timing:''' we assume that the network is synchronous.
* '''Adversarial model:''' [[coherent attacks]]
* '''Adversarial model:''' [[coherent attacks]].


==Outline==
==Outline==

Revision as of 16:09, 24 April 2019

A device-independent quantum key distribution protocol implements the task of Quantum Key Distribution (QKD) without relying on any particular description of the underlying system. The protocol enables two parties, Alice and Bob, to establish a classical secret key by distributing an entangled quantum state and checking for the violation of a Bell inequality in order to certify the security. The output of the protocol is a classical secret key which is completely unknown to any third party, namely an eavesdropper.

Tags: Two Party, Quantum Enhanced Classical Functionality, Specific Task,Quantum Key Distribution, BB84 QKD,

Assumptions

  • Network: we assume the existence of an authenticated public classical channel between Alice and Bob.
  • Timing: we assume that the network is synchronous.
  • Adversarial model: coherent attacks.

Outline

A DIQKD protocol is composed by the following steps:

  • The first phase of the protocol is the distribution. For each round of this phase:
    • Alice uses the source to prepare a maximally entangled state and send half of the state to Bob.
    • Upon receiving the state, Bob announces that he received it, and they both use their respective devices to measure the quantum systems. They record their output in a string of bits.
  • The second phase is when Alice and Bob publicly exchange classical information in order to perform error correction, where they correct their strings generating the raw keys, and parameter estimation, where they estimate the parameters of interest. At the end of this phase Alice and Bob are supposed to share the same -bit string and have an estimate of how much knowledge an eavesdropper might have about their raw key.
  • In the final phase, Alice and Bob perform privacy amplification, where the not fully secure -bit strings are mapped into smaller strings Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle K_A} and , which represents the final keys of Alice and Bob respectively.

Hardware Requirements

  • Network Stage: Entanglement Distribution
  • Relevant Network Parameters: Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \epsilon_T, \epsilon_M} (see Entanglement Distribution)
  • Distribution of Bell pairs, and measurement in three different bases (two basis on Alice's side and three basis on Bob's side).
  • Minimum number of rounds ranging from to Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \mathcal{O}(10^{12})} depending on the network parameters, for commonly used secure parameters.
  • , taking a depolarizing model as benchmark. Parameters satisfying are sufficient.
  • Authenticated classical channel.
  • Random number generator.

Notation

  • expected number of rounds
  • final key length
  • fraction of test rounds
  • quantum bit error rate
  • CHSH violation
  • expected winning probability on the CHSH game in an honest implementation
  • width of the statistical interval for the Bell test
  • confidence interval for the Bell test
  • Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \epsilon_s} smoothing parameter
  • error probabilities of the error correction protocol
  • error probability of Bell violation estimation.
  • error probability of Bell violation estimation.
  • error probability of the privacy amplification protocol
  • leakage in the error correction protocol

Properties

Either Protocol (see Pseudocode) abort with probability higher than , or it generates a
-correct-and-secret key of length

where Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \mbox{leak}_{EC}} is the leakage due to error correction step and the functions Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \bar{s}} , , and are specified in below. The security parameters of the error correction protocol, and , mean that if the error correction step of the protocol (see below) does not abort, then with probability at least , and for an honest implementation, the error correction protocol aborts with probability at most .

  • Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle \nu_1=2 \Big(\log 7 +\left\lceil\frac{|h'(\omega_{exp}+\delta_{est})|}{1-(1-\gamma)^{s_{\max}}}\right\rceil\Big)\sqrt{1-2\log\epsilon_s}}

Pseudocode

  • Input:
  • Output:

1. Distribution and measurement

  1. For every block
    1. Set and Failed to parse (SVG (MathML can be enabled via browser plugin): Invalid response ("Math extension cannot connect to Restbase.") from server "https://wikimedia.org/api/rest_v1/":): {\displaystyle C_j=\bot} .
    2. While
      1. Set
      2. Alice and Bob choose a random bit such that .
      3. If then Alice and Bob choose inputs .
      4. Else they choose (the observables for the CHSH test).
      5. Alice and Bob use their devices with the respective inputs and record their outputs, and respectively.
      6. If they set .
  • At this point Alice holds strings and Bob , all of length .

2. Error Correction

  • Alice and Bob apply the error correction protocol , communicating script in the process.
  1. If aborts, they abort the protocol
  2. Else they obtain raw keys and .

3. Parameter estimation

  1. Using and , Bob sets
    1. If and then
    2. If and then
    3. If and then
  2. He aborts If , i.e., if they do not achieve the expected violation.

4. Privacy amplification

  • is a privacy amplification subroutine
  1. Alice and Bob run and obtain secret keys ;

Further Information

contributed by Gláucia Murta