The Cut-Set Converse Bound

Why We Need a Converse

The MAN scheme of Chapter 2 achieves rate RMAN(M)=K(1βˆ’M/N)/(1+KM/N)R_{\text{MAN}}(M) = K(1-M/N)/(1+KM/N). 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 KK users, NN files, and per-user cache size MM, any scheme achieving worst-case rate RR satisfies Rβˆ—(M)β€…β€Šβ‰₯β€…β€Šmax⁑s∈{1,…,min⁑(K,N)}(sβˆ’sM⌊N/sβŒ‹).R^*(M) \;\geq\; \max_{s \in \{1, \ldots, \min(K, N)\}} \left( s - \frac{s M}{\lfloor N/s \rfloor} \right).

The bound is a cut-set argument: pick ss users, consider the channel from the caches + delivery messages (over ⌊N/sβŒ‹\lfloor N/s \rfloor rounds) to the demanded files. The caches hold sMFsM F bits at most; the delivery messages hold ⌊N/sβŒ‹RF\lfloor N/s \rfloor R F bits. Together they must encode ⌊N/sβŒ‹β‹…sβ‹…F\lfloor N/s \rfloor \cdot s \cdot F bits of file data (every file requested at least once). Rearranging gives the bound.

Example: Cut-Set Bound for K=4K = 4, N=4N = 4

Compute the cut-set lower bound for K=4K = 4, N=4N = 4, and all M∈{0,1,2,3,4}M \in \{0, 1, 2, 3, 4\}.

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 K=NK = N (symmetric), all three curves coincide; the gap is more visible at K>NK > N or K<NK < N.

Parameters
10
20

Key Takeaway

The cut-set bound sees the problem as a compressed-storage game. Each cut yields one constraint: the ss caches plus ⌊N/sβŒ‹\lfloor N/s \rfloor delivery messages must encode s⌊N/sβŒ‹s \lfloor N/s \rfloor files' worth of data. Maximizing over ss 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 β‰ˆ12\approx 12 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.