The Cut-Set Converse Bound
Why We Need a Converse
The MAN scheme of Chapter 2 achieves rate . But is this the best anyone can do? To answer that, we need a converse bound β a rate below which no scheme can go, regardless of how cleverly it is designed. This is the classical information-theoretic project: upper bound an operational quantity (rate) via information-theoretic quantities (entropies), then use entropy bounds to produce a scheme- independent lower bound on rate.
The cut-set converse of Maddah-Ali and Niesen is the first such bound for coded caching. It is not tight in general β MAN does strictly better than this bound predicts β but it establishes the structure of the answer and sets up the later exact-optimality result of YMA '18 under uncoded placement.
Theorem: Cut-Set Converse Bound
For the shared-link coded caching network with users, files, and per-user cache size , any scheme achieving worst-case rate satisfies
The bound is a cut-set argument: pick users, consider the channel from the caches + delivery messages (over rounds) to the demanded files. The caches hold bits at most; the delivery messages hold bits. Together they must encode bits of file data (every file requested at least once). Rearranging gives the bound.
Fix a cut and a demand ensemble
Fix any . Consider users, say users . We construct demand vectors such that their union covers a set of distinct files: the -th user's demands are for .
Set up the information-theoretic constraint
For each , the users must recover their demanded files from plus the delivery message . By the data processing inequality and Fano's inequality,
Union over $\ell$
The delivery messages jointly determine all files in given the caches. Concretely,
Bound the joint entropy
By subadditivity and the cache capacity: Each delivery message has rate at most :
Combine and solve
s \in {1, \ldots, \min(K, N)}\blacksquare$
Example: Cut-Set Bound for ,
Compute the cut-set lower bound for , , and all .
Enumerate $s$
Candidates: .
Compute per-$s$ bounds
- : . Bound: .
- : . Bound: .
- : . Bound: .
- : . Bound: .
Take the max over $s$
At : bounds are . Max: (with ). At : bounds are . Max: (). At : bounds are . Max: (). At : Max: . At : .
Compare with MAN
MAN at : . . : . Cut-set: . Gap factor . : . Cut-set: . Gap factor . MAN exceeds the cut-set bound by a factor that depends on . The gap is real but bounded.
MAN Achievability vs. Cut-Set Converse
The memory-load plot with both the MAN upper bound (achievable) and the cut-set lower bound (converse). The green dotted curve is the tight YMA '18 converse under uncoded placement, which we prove in Β§3.3. Notice that at (symmetric), all three curves coincide; the gap is more visible at or .
Parameters
Key Takeaway
The cut-set bound sees the problem as a compressed-storage game. Each cut yields one constraint: the caches plus delivery messages must encode files' worth of data. Maximizing over picks the tightest constraint. This is a classical cut-set argument β the same pattern that yields the max-flow min-cut bound in networks and the cut-set lower bound on broadcast channel capacity.
The Cut-Set Bound Is Loose β And That's Interesting
An honest assessment of the Maddah-AliβNiesen 2014 result is: the achievable scheme and the converse bound both exist, but they do not coincide. The multiplicative gap between MAN achievability and cut-set converse is at most in general (MN 2014 showed this), and often as low as 2β3 in practice. Closing the gap was the main research question of coded caching from 2014 to 2018.
Yu, Maddah-Ali, and Avestimehr resolved it in 2018 under the restriction of uncoded placement: they proved the MAN scheme achieves rate exactly equal to the best converse under uncoded placement, closing the gap to 1. The case of general (possibly coded) placement remains open. This is our topic for Β§3.3 and Β§3.5.