Exercises
ex-cc-ch02-01
EasyFor , , compute the MAN subpacketization , the number of coded messages, the size of each coded message, and the rate .
, messages = .
Each message has size , so bits total Γ (K-t)/(t+1).
Count
Subpacketization: . Coded messages: . Each message has size bits. Rate: . Cross-check: . β
ex-cc-ch02-02
EasyFor the MAN scheme, verify that each user's cache holds exactly bits by computing the total number of subfiles and multiplying by subfile size, for , , .
User k has subfiles in cache.
Compute
Subfiles per cache: . Subfile size: bits. Total: bits = files bits/file. Target . β
ex-cc-ch02-03
EasyState the identity and prove it from the definition of binomial coefficients.
Write the ratio as factorials and simplify.
Compute
. β
ex-cc-ch02-04
EasyFor the demand vector on , , (all users request the same file), compute the MAN delivery rate.
The MAN scheme's rate does not depend on in the worst case, but it may be smaller for specific demands.
When all are equal, many subfiles coincide in the coded messages.
Expand messages
For : . Similarly for other .
Count effective rate
When all users request , the MAN scheme's raw transmissions are still messages of size . Total: . Rate .
Observation
This equals the worst-case MAN rate . In fact the base MAN scheme sends the same messages regardless of demands when demands happen to be equal, so rate is preserved. A smarter delivery (same-demand aware) would be cheaper β but the worst-case formula already captures the right number for the default scheme.
ex-cc-ch02-05
EasyExplain in one paragraph why the XOR cancellation in MAN delivery works for any demand vector , not just specific ones.
The summands depend on , but the subfile index set depends only on .
Answer
For any demand , the coded message is . User needs and has all other summands in its cache because every other subfile's index set (for ) contains . This is the structural guarantee of the placement β it does not depend on which file each user requested.
ex-cc-ch02-06
MediumCache budget equality. Using the identity , prove carefully that user 's cache stores exactly bits, where .
Count subfiles per user, multiply by subfile size.
Count
User has subfiles in cache, each of size bits.
Simplify
Total bits: . Using the identity: .
ex-cc-ch02-07
MediumDemand-dependent vs worst-case rate. Show that under MAN delivery, if all users request the same file, the achievable rate is actually ... wait, that's not right. Actually: with all-same demands, MAN sends distinct messages (after de-duplication), because many are equal. Derive this rate.
When , depends only on , not on demand labels.
Count distinct coded messages under this structure.
Observation
For all-same demand , . This depends only on the single file and the set . No further simplification in general unless the user knows more about the file's structure.
Rate
The number of -subsets is unchanged: . Messages are still distinct (different XORs of different subfiles of ). So the rate is β same as worst case. No savings from demand concentration under the vanilla scheme.
Interpretation
A smarter scheme (demand-aware delivery) could recognize that only distinct subfiles are missing and broadcast those directly. But that's not the MAN scheme; it is a demand-adaptive variant (Chapter 18). The MAN scheme's rate is demand-agnostic by design, trading robustness for simplicity.
ex-cc-ch02-08
MediumConvex envelope vs continuous formula. For , , compute (a) the naive continuous formula and (b) the memory-shared rate from the convex envelope at . Quantify the gap.
Integer points: gives , . gives , .
Linear interpolate between them at .
Continuous
.
Memory-shared
At : . At : . Linear interp at : .
Gap
Memory-shared (3.583) exceeds continuous (3.4) by about 5.4%. The piecewise-linear envelope is slightly above the continuous curve everywhere except at integer- points.
ex-cc-ch02-09
MediumShow the coded gain is tight. Prove that for any demand vector under MAN delivery, at most users can be simultaneously satisfied by a single XOR message.
An XOR of summands benefits at most users simultaneously.
In MAN, each is an XOR of summands.
Bound users per message
A coded message has summands. Each summand is needed by exactly one user (since the index excludes ). Hence the message serves at most distinct users, with equality when demands are such that each summand is actually missing for its designated user.
Interpretation
The coded caching gain is the maximum multicast gain attainable by XOR combining subfiles under the MAN structure. To exceed it would require a different placement (e.g., coded placement, which we explore in Ch 13) or a different algebraic structure (linear combinations, index coding, Ch 4).
ex-cc-ch02-10
MediumSubpacketization scaling. For fixed memory ratio , what value of makes the subpacketization exceed the number of bits in a 4 GB video file ( bits)? Use the Stirling approximation .
.
Set and solve for .
Solve
. .
Interpret
For , subpacketization exceeds the video file size β each "subfile" is less than one bit. This is the operational reason MAN does not scale to wireless networks with hundreds of users. Chapter 14's graph-coloring and PDA constructions handle + with polynomial .
ex-cc-ch02-11
MediumDecentralized placement (preview). In a decentralized version of MAN (Maddah-AliβNiesen 2015), each user independently caches each bit with probability , with no coordination. Show that the rate-memory tradeoff approaches the centralized MAN formula as .
Expected cache size: each bit cached iid with prob ; total bits.
Subfile of : bits cached by exactly users in .
Expected subfile sizes
A bit of is cached by subset with probability . So subfile has expected size bits.
Delivery rate
Mimic MAN: send XOR for each of size . In the limit , subfiles concentrate at their expected sizes, and the rate approaches . For large, , the same asymptote as centralized MAN.
Operational point
Decentralized MAN eliminates the need for server-coordinated placement β each user acts independently. The asymptotic rate matches; the finite- performance is strictly worse by a small multiplicative factor.
ex-cc-ch02-12
HardProof: decoding only requires the -subsets containing . Prove rigorously that user can decode from the messages with , and that the other messages (with ) are unnecessary for user .
Messages with deliver subfiles β exactly the missing ones.
Messages with have no summand indexed by β they carry no useful information to user .
Sufficiency
Missing subfiles for user : for every -subset . Such a corresponds to the -subset , and the message has as one summand. The other summands are in user 's cache (by the placement rule), so user XOR-cancels and recovers . Repeating across all , user collects all missing subfiles.
Necessity of only the $k \in \mathcal{S}'$ messages
Any message with is an XOR of subfiles indexed by subsets for . None of these subsets is the form ; the file labels are for . Hence carries no information about 's subfiles β irrelevant to user .
Message count check
-subsets containing : . Missing subfiles: . One-to-one correspondence. β
ex-cc-ch02-13
HardGeneralized MAN with coded placement (Chen-Fan-Letaief). Prove that any placement in which subfile is cached by all users in , for any chosen family of subsets (not necessarily all -subsets), admits a delivery rate of (number of distinct -subsets such that is in the family, for some ) / . Is this always at least the MAN rate?
Generalize the XOR construction to an arbitrary family.
Consider trivial subfamilies and whether they degrade rate.
Generalized scheme
Fix a family of subsets of . For every , subfile is in caches . Delivery: for every subset of such that for every , send .
Rate
Total delivery: (number of valid ) Γ (subfile size). This depends on β the base MAN corresponds to , and yields the rate formula with subpacketization .
Sub-optimality possibility
Smaller yields fewer valid (shorter delivery) but also fewer subfiles (larger subfiles, same cache budget). There is an optimization: the base MAN maximizes multicast gain; PDAs (Chapter 14) shrink to polynomial size at a rate cost. The result here is the blueprint for PDA constructions.
ex-cc-ch02-14
ChallengeThe asymptotic gain formula. Prove that as with fixed memory ratio , Interpret this limit: what does it say about the fundamental link-load scaling under coded caching?
Divide numerator and denominator by .
Think about what this says about per-user efficiency.
Direct limit
. Divide top and bottom by : as .
Interpretation
The shared-link load per delivery round is bounded by a constant β independent of . Equivalently, the link-load per user is : the marginal cost of adding a user vanishes. This is the killer scaling feature of coded caching, and is why it is regarded as fundamental for future CDN architectures.
Pathological cases
At : (no caching, no gain). At : (all files cached). The limit interpolates these two extremes smoothly.
ex-cc-ch02-15
ChallengeProve the MAN scheme is a valid scheme even for partially non-distinct demands. Show that if (two users request the same file), both users still decode their (common) requested file correctly under the stated delivery.
Trace through the XOR cancellation with .
The missing subfiles for both users are indexed by the same -subsets not containing them (different for each user).
Setup
Both users want . User 1 is missing for with . User 2 is missing for with . Some missing subfiles overlap (those with ), some are user-specific.
Decoding
For a missing subfile with : Let . Message . For : summand is (the target). For : summand is . This summand is in user 1's cache iff , which is true since is in the set. β User 1 decodes the target.
Symmetry for user 2
If (so contains 2 but not 1), then means the summand for in is . This is user 2's cache iff , which is false. So user 2 does not cache this summand β but user 2 also does not need (since ), so user 2 doesn't use this message. Both users successfully collect the subfiles they need. β