Prerequisites & Notation
Before You Begin
Chapter 14 extends classical PIR (Chapter 13) along three orthogonal axes: coded storage instead of replication (§14.1), -colluding databases (§14.2), and two-sided privacy via SPIR (§14.3). Section §14.4 sketches what is known when these extensions are combined. Each section relies on the same finite-field IA core as Chapter 13 — the novelty is in how the constraints alter the achievable rate region.
- Sun-Jafar PIR capacity (Chapter 13 §13.3)(Review ch13)
Self-check: State the formula and identify each term's role.
- MDS codes and Singleton bound (background)(Review ch04)
Self-check: For an -MDS code, what is the minimum distance, and how many erasures can be corrected?
- Shamir secret sharing (Chapter 3)(Review ch03)
Self-check: Why does the -private constraint force polynomial degree in Shamir-type schemes?
- Cut-set converse recipe (Chapter 2)(Review ch02)
Self-check: Apply the four-step recipe (cut → entropy bound → symmetrize → normalize) to a generic retrieval problem.
Notation for This Chapter
Chapter 14 inherits the PIR notation from Chapter 13 ( databases, files, desired index) and adds:
| Symbol | Meaning | Introduced |
|---|---|---|
| MDS-code dimension: any databases reconstruct the full library | s01 | |
| Maximum colluding subset size; privacy holds against any databases | s02 | |
| An arbitrary subset of with | s02 | |
| Capacity for -MDS coded-storage PIR | s01 | |
| Capacity for -colluding PIR with replicated storage | s02 | |
| Capacity for symmetric PIR (two-sided privacy) | s03 | |
| Common randomness shared across databases (used in SPIR) | s03 | |
| Shannon entropy | s03 |