2016
DOI: 10.1109/tit.2016.2557804
|View full text |Cite
|
Sign up to set email alerts
|

Hierarchical Coded Caching

Abstract: Caching of popular content during off-peak hours is a strategy to reduce network loads during peak hours. Recent work has shown significant benefits of designing such caching strategies not only to deliver part of the content locally, but also to provide coded multicasting opportunities even among users with different demands. Exploiting both of these gains was shown to be approximately optimal for caching systems with a single layer of caches.Motivated by practical scenarios, we consider in this work a hierar… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
261
0

Year Published

2016
2016
2024
2024

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 265 publications
(264 citation statements)
references
References 27 publications
3
261
0
Order By: Relevance
“…where T LB (d(U), χ) is given by (36) for each reordered demand vector d(U) ∈ D L . Rewriting the summation in (42), we get…”
Section: Information Theoretic Conversementioning
confidence: 99%
“…where T LB (d(U), χ) is given by (36) for each reordered demand vector d(U) ∈ D L . Rewriting the summation in (42), we get…”
Section: Information Theoretic Conversementioning
confidence: 99%
“…In [3] it shows that R HCC-C,1 and R HCC-C,2 achieve the optimal rates to within a constant multiplicative and additive gap.…”
Section: A Preliminarymentioning
confidence: 97%
“…In [3] the authors considered the two-layer network as described in Section II. They propose three hierarchical caching schemes, namely HCC-A, HCC-B and HCC-C, based on the single-layer decentralized caching scheme.…”
Section: A Preliminarymentioning
confidence: 99%
See 1 more Smart Citation
“…Note that these constraints differ slightly from the original constraints in [30] in that the parameters a r,0 , for 0 ≤ r < K R are present in (2) and (3) but not in [30,Eq. (13) and (14)]. This is because [30] assumed that every bit of a file must be either cached in at least one EN or cached in all UEs if not in any EN due to the absence of the fronthaul network.…”
Section: Following This Placement Strategy Each En Cachesmentioning
confidence: 99%