The MAN Scheme at a Glance
The MAN Scheme on One Page
Before we dive into proofs, here is the entire Maddah-AliβNiesen scheme in one page. It works when is an integer (non-integer is handled by memory sharing, Β§2.5).
Placement (off-peak). Split each file into equal-sized subfiles, one per -subset of : Each subfile has size bits. Place subfile in the cache of user if and only if .
Delivery (peak). For each -subset , send the coded message There are such messages, each of size .
Rate.
That is the entire scheme. The rest of this chapter spells out why it works and verifies the claims.
Definition: The Maddah-AliβNiesen (MAN) Scheme
The Maddah-AliβNiesen (MAN) Scheme
Fix , , with . The Maddah-AliβNiesen (MAN) scheme consists of the following placement and delivery algorithms.
Placement. Each file is split into subfiles of equal size , indexed by -subsets . The cache of user is That is, user holds every subfile whose index set contains .
Delivery. On demand vector , for every -subset , the server broadcasts The XOR is over (bitwise).
Key Takeaway
Each coded message simultaneously serves exactly users β namely all . For each , user can recover because every other summand (with ) is already in user 's cache (since ). This is the coded multicasting gain in its purest form.
MAN Placement (K=3, t=1)
MAN Delivery β One XOR Serves Users
Example: Walkthrough: , , Files
Take , , (so ). Execute the MAN scheme for demand .
Split files
Each file is split into subfiles: and . Each subfile has size bits.
Populate caches
User 1's cache: , total size = bits (). β User 2: . User 3: .
Delivery: enumerate $(t+1)$-subsets
-subsets of : . Three coded messages.
.
.
.
Verify each user decodes
User 1 receives . It has in its cache, so from it recovers . From it recovers . It already has . Done: all three subfiles of . β
User 2 already has . From with in cache: decodes . From with in cache: decodes . All three subfiles of . β
User 3: already has . From : recovers . From : recovers ... wait, user 3 needs 's subfiles, but contains . User 3 has in cache, so it decodes . β
Compute the rate
3 messages, each of size bits: total bits. Rate file. MAN formula: . Wait β let me recompute with : . β Match.
Placement Structure β Which Subfile Goes to Which User?
Visualize the MAN placement as a heatmap: rows are subfiles (indexed by -subsets of ), columns are users. A filled cell means subfile is placed in user 's cache. Each row has exactly filled cells (subfile in caches); each column has filled cells (user holds that many subfiles per file).
Parameters
MAN subfile
A subfile of file indexed by a -subset . Every subfile has equal size bits, and subfile is stored in the caches of exactly the users .
Related: Coded multicasting
Coded multicasting
The delivery-phase technique of sending a single XOR-coded message that simultaneously satisfies users, one per element of . This is the core combinatorial gain of the MAN scheme, distinguishing it from uncoded delivery.
Related: MAN subfile, Coded caching gain
Coded caching gain
The multiplicative factor by which the MAN scheme's delivery rate is smaller than the uncoded rate . For large, the gain is unbounded.
Related: Coded multicasting