The Multi-Server MAN Scheme
Generalizing MAN to Multiple Transmitters
The single-server MAN scheme (Chapter 2) sends XOR messages in sequence. With cooperating servers, we can send multiple messages in parallel β one per server β provided the messages don't interfere at the receivers. Zero-forcing across aggregate antennas lets us do this.
This section describes the multi-server MAN scheme: the same combinatorial placement as standard MAN, with an adapted delivery phase that exploits both coded multicasting and cooperative MIMO. The rate (in file units) is simply β scale the single-server rate by the number of cooperating servers. The DoF matches Theorem 9.1.
Multi-Server MAN Delivery
Complexity: Per -subset: coded streams, each serving users. Total messages: subsets Γ streams = . Each message of size . Total bits: . Delivery time: scales as channel uses.The scheme requires joint precoding across servers: each server's transmit signal is a function of all users' demands and all servers' channels. This is the "full cooperation" assumption.
Theorem: Multi-Server MAN Achievability
The multi-server MAN scheme with cooperating -antenna servers achieves sum-DoF , matching the Lampiris-Caire formula with effective .
The servers are treated as a single transmitter with antennas by joint precoding. All of Chapter 5's analysis applies verbatim.
Consolidation
Under full cooperation, the servers emit a joint signal vector from the perspective of users. This is identical to a single -antenna transmitter.
Apply Chapter 5
The cache-aided -antenna BC has DoF by Theorem 5.1 (Lampiris-Caire).
Per-server rate
The per-server transmit rate is DoF per channel use β scaled by versus the single-server case.
Per-Server Rate vs Memory Ratio
Per-server delivery rate under cooperative multi-server MAN. With cooperating servers, each server's load is β the aggregate rate is the same as single-server MAN, but split across servers.
Parameters
Example: Multi-Server MAN: , , ,
Work through the multi-server MAN delivery for users, cooperating servers (each with antenna), (so ), demand .
Placement
MAN, : each file split into subfiles . User caches .
Effective antennas
. Group size for Lampiris-Caire: .
Delivery groups
-subsets of : . Four groups; each group beams.
Per-group beams
For group : two ZF beams. Beam 1 target (null user 3): . Beam 2 target (null user 2): .
Per-server signals
Cooperative precoder: where zero-forces across the two antennas (one per server).
Decoding
Each user in the group receives its targeted beam (the other is nulled); XOR-cancels using cached subfiles.
Rate
4 groups Γ 2 beams Γ 1 channel use per beam = 8 beam-channel-uses. Each beam delivers 1 subfile-sized message = bits. Total transmission time: normalized DoF = ; per-user DoF = 3/4. Compare single-server: DoF = , per-user 0.5. Cooperation gives 1.5Γ DoF improvement.
Multi-Server Cooperation in Practice
Deployed multi-server cooperation schemes:
- 3GPP CoMP (Rel-11+). Coordinated multi-point transmission; up to 3-cell cooperation typical. Latency budget: ~10 ms for shared data exchange.
- 5G Joint Transmission (JT-CoMP). Data is simultaneously sent from multiple cells with cooperative precoding. Used in dense deployments.
- 6G cell-free massive MIMO. Envisioned cooperating APs; requires dedicated fronthaul infrastructure.
For cache-aided multi-server systems, the inter-server communication requirement is higher than for uncoded CoMP: servers must also coordinate on which MAN subfiles each holds, and on the XOR structure of delivery. Realistic scale: per cluster with full cooperation, time-shared between clusters.
- β’
CoMP Rel-11: up to 3 cooperating cells per cluster
- β’
Joint Transmission: requires ~1 ms latency for data sharing
- β’
Cell-free mMIMO (6G vision): 10-100 APs cooperating
- β’
Cache coordination: aligned placement required across servers
Partial Cooperation
When full cooperation is infeasible, one falls back to partial cooperation:
- Cluster cooperation. Group servers into clusters of size ; full cooperation within cluster, time-share between clusters. DoF reduces from to per cluster, averaged.
- Non-cooperative coded caching. Each server independently runs MAN. No DoF gain from ; each server handles users. Rate per server: . This is the worst case.
Typical deployment: . With and , cluster DoF = β substantial even at moderate cluster sizes.