Retrieving and routing quantum information in a quantum network

From MaRDI portal




Abstract: In extant quantum secret sharing protocols, once the secret is shared in a quantum network ( extsc{qnet}) it can not be retrieved back, even if the dealer wishes that her secret no longer be available in the network. For instance, if the dealer is part of two extsc{qnet}s, say mathcalQ1 and mathcalQ2 and subsequently finds that mathcalQ2 is more reliable than mathcalQ1, the dealer may wish to transfer all her secrets from mathcalQ1 to mathcalQ2. In this work we address this problem by designing a protocol that enables the source/dealer to bring back the information shared in the network, if desired. Unlike classical revocation, no-cloning-theorem automatically ensures that the secret is no longer shared in the network. The implications of our results are multi-fold. One interesting implication of our technique is the possibility of routing qubits in asynchronous extsc{qnets}. By asynchrony we mean that the requisite data/resources are intermittently available (but not necessarily simultaneously) in the extsc{qnet}. For example, we show that a source S can send quantum information to a destination R even though (a) S and R share no quantum resource, (b) R's identity is {em unknown}/ to S initially, (c) S herself can be R at a later date and/or in a different location to bequeath her information and (d) the path chosen for routing the secret may hit a dead-end due to resource constraints. Another implication of our technique is the possibility of using {em insecure}/ resources. For instance, it may safely store its private information with a neighboring organization without revealing data to the host and losing control over retrieving the data. Putting the two implications together, namely routing and secure storage, it is possible to envision applications like quantum mail (qmail) as an outsourced service.









This page was built for publication: Retrieving and routing quantum information in a quantum network

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q264891)