English

Sun-Jafar-Type Schemes for Weak Private Information Retrieval

Information Theory 2025-01-22 v1 math.IT

Abstract

In information-theoretic private information retrieval (PIR), a client wants to retrieve one desired file out of MM files, stored across NN servers, while keeping the index of the desired file private from each TT-sized subset of servers. A PIR protocol must ideally maximize the rate, which is the ratio of the file size to the total quantum of the download from the servers, while ensuring such privacy. In Weak-PIR (WPIR), the criterion of perfect information-theoretic privacy is relaxed. This enables higher rates to be achieved, while some information about the desired file index leaks to the servers. This leakage is captured by various known privacy metrics. By leveraging the well-established capacity-achieving schemes of Sun and Jafar under non-colluding (T=1T=1) and colluding (1<TN1<T\leq N) scenarios, we present WPIR protocols for these scenarios. We also present a new WPIR scheme for the MDS scenario, by building upon the scheme by Banawan and Ulukus for this scenario. We present corresponding explicit rate-privacy trade-offs for these setups, under the mutual-information and the maximal leakage privacy metrics. In the collusion-free setup, our presented rate-privacy trade-off under maximal leakage matches that of the previous state of the art. With respect to the MDS scenario under the maximal leakage metric, we compare with the non-explicit trade-off in the literature, and show that our scheme performs better for some numerical examples. For the TT-collusion setup (under both privacy metrics) and for the MDS setup under the mutual information metric, our rate-privacy trade-offs are the first in the literature, to the best of our knowledge.

Keywords

Cite

@article{arxiv.2501.11505,
  title  = {Sun-Jafar-Type Schemes for Weak Private Information Retrieval},
  author = {Chandan Anand and Jayesh Seshadri and Prasad Krishnan and Gowtham R. Kurri},
  journal= {arXiv preprint arXiv:2501.11505},
  year   = {2025}
}
R2 v1 2026-06-28T21:11:22.617Z