D2D vs Infrastructure Delivery
Two Delivery Paradigms
Having established the scaling for D2D caching, we now compare it against infrastructure-based delivery (cellular base station, possibly with MAN caching). This comparison reveals when D2D is preferable: typically in dense, local, low-mobility scenarios; when it is not: typically in sparse or long-range scenarios where D2D neighbor density is too low.
The design implication is that neither paradigm is universally better. Real 6G networks will likely combine the two: cellular infrastructure for low-density regions and wide-area coverage, with D2D caching offloading dense local traffic.
Theorem: D2D vs Infrastructure Throughput
For the D2D caching network with users, cache , library , and protocol interference model:
where is the per-user throughput of an infrastructure-based network serving all users through a single base station. D2D dominates infrastructure as grows.
Infrastructure: all users share a single downlink of bounded capacity; each gets . With MAN caching, the shared capacity grows as at best β still per user for fixed .
D2D: local communication bypasses the shared bottleneck; per-user throughput is constant in . The advantage of D2D is .
Infrastructure bound
With single BS serving users, total downlink capacity is (classical capacity bound for interference-limited cellular). Per-user: .
D2D bound
From Theorem 10.1: per-user throughput , constant in .
Ratio
for fixed . D2D is asymptotically much better per user.
Caveat
The bound is asymptotic. For small , infrastructure can outperform D2D due to neighbor-sparsity. The crossover is around - depending on density and cell size.
D2D vs Infrastructure Throughput
Compare per-user throughput of three schemes: (blue) D2D + caching = ; (red) infrastructure + MAN = ; (green) infrastructure no cache = . D2D's advantage grows with cache ratio and network size.
Parameters
Example: Small vs Dense D2D Network
(a) A small office network: users, files, files (). Compare D2D and cellular per-user throughput. (b) A dense stadium: users, same per-user cache.
(a) Office
D2D: β constant. But with only 10 users, the "" constant may be small due to few neighbors. Cellular: . Cellular may actually win at this because D2D's constant factor is small.
(b) Stadium
D2D: , same. With 10,000 users, the constant factor reaches its full asymptotic value. Cellular: . Cellular collapses.
Crossover
The crossover between "cellular better" and "D2D better" is around - for typical densities. Below that, cellular wins; above, D2D wins.
Hybrid design
Deploy both: D2D for popular/local content; cellular (with MAN) for unpopular/wide-area content. Mixed-architecture designs beat either alone; see Ji-Caire-Molisch 2018 hybrid-scheme extension.
Local Reuse Rate Under Zipf Popularity
For Zipf popularity, the fraction of requests servable by local D2D caches is a non-linear function of . High-popularity files benefit disproportionately from small caches; diminishing returns at higher .
Parameters
Key Takeaway
D2D + caching dominates infrastructure at scale ( large). Per-user throughput: for D2D, for infrastructure. The crossover occurs around . At stadium / urban densities, D2D is the only option for maintaining per-user rate.
Hybrid D2D + Infrastructure Networks
Real deployments will combine D2D and infrastructure:
- Tiered offloading. Base station handles wide-area, high- capacity, low-latency content. D2D offloads local, popular, latency-tolerant content.
- Cache pre-population. BS pre-places content in D2D-reachable areas (stadiums, malls, residential blocks). D2D then serves the cached content locally.
- Signaling. BS provides device discovery and pairing information. D2D does the delivery.
- Charging. Users pay for D2D contribution (or ISP pays users who participate). Business model is key.
6G vision (3GPP Rel-19+ study items): cache-aided D2D for XR and video. Analysis of this hybrid architecture is a major CommIT research topic.
- β’
3GPP LTE Rel-12 ProSe: direct discovery and communication
- β’
5G NR Sidelink Rel-16+: V2X and basic D2D
- β’
6G study items (Rel-19/20): cache-aided D2D, MBSFN extensions
- β’
Energy cost: D2D transmitter ~100 mW vs cellular ~500 mW
Common Mistake: Density Assumption Matters
Mistake:
Quoting D2D throughput for networks that are too sparse (neighbors too few).
Correction:
The scaling assumes a dense network where each user has neighbors within D2D range. In sparse deployments (e.g., rural, low-density), this assumption fails: neighbors are few, local hit probability is low, effective throughput is reduced.
For sparse networks, infrastructure dominates. The correct interpretation of Ji-Caire-Molisch is: D2D is a dense-network regime result. At sparse deployment density, Gupta-Kumar-style scaling is the regime.
Historical Note: From Gupta-Kumar to D2D Caching
2000β2016The story of wireless ad-hoc scaling started pessimistically:
- 2000: Gupta and Kumar established the celebrated scaling for ad-hoc throughput. Per-user rate . Widely interpreted as "ad-hoc doesn't scale."
- 2002-2010: Franceschetti-Migliore-Minero variations; Franceschetti-Dousse-Tse on percolation. Constants improved, but the scaling persisted.
- 2016: Ji, Caire, Molisch broke the barrier: with caching, per-user throughput is constant, . This is the first throughput result in ad-hoc wireless that does not decay with .
The result is not just an asymptotic curiosity: it justifies the architectural paradigm of user-driven content delivery, which underpins many 6G / cell-free / MEC designs.