Editing
(Symmetric) Private Information Retrieval
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
<!-- This is a comment. You can erase them or write below --> <!-- Functionality page describes a general task which can be realised in a quantum network --> ==Description== <!-- Description: A lucid definition of functionality in discussion.--> Private information retrieval (PIR) is a classical cryptographic functionality that allows one party (user) to privately retrieve an element from a classical database owned by another party (server), i.e., without revealing to the other party which element is being retrieved (user privacy).<br></br> Symmetric private information (SPIR) retrieval is PIR with the additional requirement that throughout and after the protocol, the user remains oblivious to other database elements, i.e., apart from the queried one (data privacy).<br></br> In the quantum setting, the use of quantum systems is allowed to achieve (S)PIR: this may imply the use of a quantum channel between the user and the server, and the capability to prepare quantum states, apply quantum gates or measure quantum systems by one or both parties. (S)PIR in this setting is known as quantum (symmetric) private information retrieval (Q(S)PIR).<br></br> In the classical or quantum setting, (Q)SPIR and one-out-of-n (quantum) [[Oblivious Transfer|oblivious transfer]] (OT) are similar cryptographic tasks; the only minor difference between those functionalities is that protocols for OT are two-party protocols, while attempts at achieving SPIR have considered both two-party and multi-party protocols where the user communicates with several servers, each holding a copy of the database.<br></br> Apart from using quantum techniques to enhance the classical (S)PIR functionality (i.e., design better protocols than their classical counterparts in terms of different metrics like e.g., communication complexity), there has also been a recent interest in a ‘fully’ quantum (S)PIR where a user wants to query a quantum database (items are quantum states)[[#References|[1]]].<br></br> '''Tags:''' [[:Category:Two Party Protocols|Two Party Protocol]],[[Category:Two Party Protocols]] [[:Category:Specific Task|Specific Task]], [[Category:Specific Task]] [[:Category: Quantum Enhanced Classical Functionality|Quantum Enhanced Classical Functionality]].[[Category:Quantum Enhanced Classical Functionality]] <!-- Tags Any related page or list of protocols is connected by this section--> ==Use-cases== <!-- Use Case (if available) analyses how practical the protocol is--> ===Classical database=== *Location-based services (to protect user location privacy). *Queries of electronic medical records (these require decades of information confidentiality; hence security against quantum computing based attacks is necessary) or medical test reports. *Music and film streaming (user does not want his/her tastes to be revealed to the server). *Pay-per-view services, where the user should pay a fee to access every single database element. Quantum (S)PIR protocols may be preferred to their classical counterparts to: *Achieve (S)PIR with better communication complexity: this is convenient in the case of large databases. *Achieve (S)PIR with better security: for instance, to secure classical channels as in [[#References|[5]]]. ==Properties== <!-- All properties that should be satisfied by any protocol achieving the concerned functionality and other common terminologies used in all the protocols.--> ===Security definitions=== (Quantum) private information retrieval protocols are said to be secure if they satisfy the following conditions: *'''Correctness''': assuming that all the parties in the protocol are honest, then the output of the protocol on the user’s side must be the queried database element. *'''User privacy''': assuming that the user is honest, then, throughout the protocol, any query of the user to a server leaks no information about the desired database item. In addition to the above requirements, symmetric (quantum) private information retrieval protocols must also satisfy the following condition: *'''Data(base) privacy''': assuming that the server(s) is (are) honest(s), then, throughout the protocol, the user is unable to obtain any information beyond a single database element. ===Cost parameters=== The most common cost parameter used to characterise a given (Q)(S)PIR protocol is: *'''Communication complexity''': total number of (qu)bits exchanged between the user and the server(s) throughout the protocol. For (Q)(S)PIR protocols in general: *'''(Q)(S)PIR capacity''': maximal achievable ratio of the retrieved database element size to the total download size. Some less common cost parameters include: *'''Storage overhead''' (for multi-database (Q)(S)PIR protocols): ratio between the total number of (qu)bits stored on all servers and the number of (qu)bits in the (resp. quantum) classical database. *'''Access complexity''': total amount of data to be accessed by the server(s) for answering queries throughout a (Q)(S)PIR protocol. ==Protocols== <!-- List of different types of example protocol achieving the functionality--> ===Classical database=== In the quantum setting, protocols aiming at achieving (S)PIR for a ''classical'' database fall into two main categories: ====Single-database protocols==== As in the classical setting, in the case of the database being owned by a ''single'' server, the trivial solution (downloading the whole database) is the only way to achieve information-theoretically secure PIR – even in the case of a specious (may deviate from the protocol if its malicious operations are unknown to the user) server [[#References|[2]]]. <br> As for (quantum or classical) SPIR, it is impossible to achieve information-theoretic security with a single-server; this result was proved in the quantum setting by Lo [[#References|[3]]]. Intuitively, this comes from the fact that the (unique) trivial solution of information-theoretically secure PIR is the worst in terms of data privacy. Therefore, to design efficient PIR protocols or to achieve SPIR, several assumptions have been considered; they include: * Hardness assumptions: PIR protocols with computational security. * Assumptions on the adversarial model: ** to achieve SPIR: cheat-sensitive protocols (also known as quantum private queries (QPQ) protocols) where it is assumed that the server will not cheat if there is a non-zero probability that he will be caught cheating. ***[[Quantum Private Queries Protocol Based on Quantum Oblivious Key Distribution|QPQ protocols based on quantum oblivious key distribution]] ***[[Quantum Private Queries Protocol Based on Quantum Random Access Memory|QPQ protocols based on quantum random access memory]] ** to achieve efficient PIR: assuming an honest server. ***[[Single-Database Quantum Private Information Retrieval in the Honest Server Model|QPIR protocols in the honest server model]] * Prior shared entanglement between server and user: in the honest server model, efficient PIR protocols exist, however for a specious or malicious server, the trivial solution is optimal for PIR[[#References|[4]]]. **[[Single-Database Quantum Private Information Retrieval with Prior Shared Entanglement in the Honest Server Model|QPIR protocols with prior shared entanglement in the honest server model]] * Relativistic assumptions: quantum SPIR protocols whose security uses properties from special relativity. **[[Relativistic Quantum Oblivious Transfer|Relativistic QOT protocols]] ====Multi-database protocols==== It is possible to achieve information-theoretic (S)PIR with reduced communication complexity (i.e., compared to this of the trivial solution) by considering several servers instead of one, each holding a copy of the database, and with the help of extra assumptions. Usually, to achieve (S)PIR, it is assumed that the servers cannot communicate with each other during and after the protocol ended (no-communication assumption), and that servers share randomness (in the symmetric case only). Examples of such protocols are: * [[Multi-Database Quantum Symmetric Private Information Retrieval without Shared Randomness|Quantum multi-database SPIR protocols without shared randomness]] (replaced by prior shared entanglement between servers) * [[Multi-Database Classical Symmetric Private Information Retrieval with Quantum Key Distribution|Classical multi-database SPIR protocols with QKD secured classical channels]] * [[Multi-Database Quantum Symmetric Private Information Retrieval for Communicating and Colluding Servers|Multi-database quantum (S)PIR protocols for communicating and colluding servers]] – to do without the no-communication assumption * [[Multi-Database Quantum Symmetric Private Information Retrieval for Coded Servers|Multi-database quantum (S)PIR protocols for coded servers]] ===Quantum database=== For the case of a ''quantum'' database, the trivial solution of downloading the whole database is proved to be optimal for one-round QPIR, and for multi-round QPIR in the blind setting (i.e., the servers do not have a classical description of the quantum states of the database) and for the honest server model (and any other attack model)[[#References|[1]]].<br> Prior shared entanglement between the user and the server allows for efficient one-server QPIR protocols in the honest server model and in the blind setting. Multi-database QSPIR protocols for a quantum database with pure states, in the visible setting (servers know a classical description of the quantum database elements) exist as shown by Song and Hayashi [[#References|[1]]]. * [[Single-Database Quantum Private Information Retrieval for a Quantum Database|Single-database quantum PIR protocols in the honest server model and in the blind setting for a quantum database]] * [[Multi-Database Quantum Symmetric Private Information Retrieval for a Quantum Database|Multi-database quantum SPIR protocols in the visible setting for a quantum database]] ==Further Information== <!-- Any issue that could not be addressed or find a place in the above sections or any review paper discussing a feature of various types of protocols related to the functionality. --> ===Optimal communication complexity of the (Q)(S)PIR problem=== Below are summarised known bounds for the communication complexity of information-theoretically secure (S)PIR protocols in the classical and quantum settings, for a quantum or classical database. *<math>f</math> : number of database elements (quantum states in the 'fully' quantum setting) *<math>m</math> : total size of database elements (i.e., the sum of the sizes, in bits, of each database element) *<math>d</math> : dimension of the quantum states stored in the quantum database (<math>d=2</math> if they are qubits) *<math>k</math> : number of servers (or equivalently of replicated databases) ====Single-database case==== {| class="wikitable plainrowheaders" ! scope="col" | Problem ! scope="col" | Additional assumptions ! scope="col" | Optimal communication complexity ! scope="col" | Reference |- ! scope="row" | Classical PIR | || <math>\Theta(m)</math> || [http://www.wisdom.weizmann.ac.il/~oded/PSX/pir2.pdf Chor et al (1995)] |- ! scope="row" | Classical SPIR | || NA (impossible) || |- ! scope="row" rowspan="4" | Quantum PIR (Classical database) | Specious server || <math>\Theta(m)</math> || [https://arxiv.org/pdf/1304.5490.pdf Baumeler and Broadbent (2015)] |- | Specious server & prior entanglement || <math>\Theta(m)</math> || [https://arxiv.org/pdf/1902.09768.pdf Aharonov et al (2019)] |- | Honest server || <math>O(poly \log (m))</math> || [https://repository.ubn.ru.nl/bitstream/handle/2066/155747/155747.pdf Kerenidis et al (2016)] |- | Honest server & prior entanglement || <math>O(\log (m))</math> || [https://repository.ubn.ru.nl/bitstream/handle/2066/155747/155747.pdf Kerenidis et al (2016)] |- ! scope="row" rowspan="2" | Quantum SPIR (Classical database) | || NA (impossible) || [https://arxiv.org/pdf/quant-ph/9611031.pdf Lo (1997)] |- | The server will not cheat if there is a non-zero probability of being caught cheating & imperfect data privacy (the user should get at most two database items) || <math>O(\log (m))</math> || [https://arxiv.org/pdf/0708.2992.pdf Giovannetti et al (2008)] |- ! scope="row" rowspan="3" | Quantum PIR (Quantum database) | Honest server & blind setting || <math>\Theta(m)</math> || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |- | Honest server & visible setting || <math>\Theta(m)</math> (for one-round) || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |- | Honest server & prior entanglement || <math>O(\log (m))</math> || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |- ! scope="row" | Quantum SPIR (Quantum database) | || || |} ====Multi-database case==== {| class="wikitable plainrowheaders" ! scope="col" | Problem ! scope="col" | Additional assumptions ! scope="col" | Optimal communication complexity ! scope="col" | Reference |- ! scope="row" | Classical PIR | || || |- ! scope="row" | Classical SPIR | Servers do not communicate with each other & secure classical channels || <math>O(m^{\frac{1}{2k-1}}) \text{ bits}</math> || [https://dl.acm.org/doi/abs/10.1145/276698.276723 Gertner et al (2000)] |- ! scope="row" | Quantum PIR (Classical database) | || || |- ! scope="row" rowspan="2" | Quantum SPIR (Classical database) | Servers do not communicate with each other || <math>O(m^{\frac{1}{2k-1}}) \text{ bits}+ \text{ comm. complexity of QKD}</math> || [https://www.mdpi.com/1099-4300/23/1/54/htm Kon and Lim (2021)] |- | Servers do not communicate with each other & honest user & prior entanglement || <math>m^{O(\log \log (k)/k \log(k))}</math> || [https://arxiv.org/pdf/quant-ph/0307076.pdf Kerenidis and de Wolf (2004)] |- ! scope="row" | Quantum PIR (Quantum database) | || || |- ! scope="row" rowspan="3" | Quantum SPIR (Quantum database) | Servers do not communicate with each other & prior entanglement & visible setting & database contains pure qubit states || <math>O(f) \text{ bits} + O(1) \text{ qubits} + O(1) \text{ ebits}</math> || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |- | Servers do not communicate with each other & prior entanglement & visible setting & database contains pure qudit states || <math>O(f) \text{ bits} + O(d^d \log (d)) \text{ qubits} + O(d^d \log (d)) \text{ ebits}</math> || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |- | Servers do not communicate with each other & prior entanglement & visible setting & database contains commutative unitaries || <math>O(f) \text{ bits} + O(\log (d)) \text{ qubits} + O(\log (d)) \text{ ebits}</math> || [https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] |} ==References== #[https://arxiv.org/pdf/2101.09041.pdf Song and Hayashi (2021)] #[https://arxiv.org/pdf/1304.5490.pdf Baumeler and Broadbent (2015)] #[https://arxiv.org/pdf/quant-ph/9611031.pdf Lo (1997)] #[https://arxiv.org/pdf/1902.09768.pdf Aharonov et al (2019)] #[https://www.mdpi.com/1099-4300/23/1/54/htm Kon and Lim (2021)] <div style='text-align: right;'>''*contributed by Marine Demarty''</div>
Summary:
Please note that all contributions to Quantum Protocol Zoo may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Quantum Protocol Zoo:Copyrights
for details).
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
News
Protocol Library
Certification Library
Nodal Subroutines
Codes Repository
Knowledge Graphs
Submissions
Categories
Supplementary Information
Recent Changes
Contact us
Help
Tools
What links here
Related changes
Special pages
Page information