Hotplug Placement Delivery Arrays (HpPDAs)
- HpPDAs are a combinatorial framework for centralized coded caching that decouples placement and delivery to accommodate unknown offline users.
- They leverage a dual-array structure—using a star-only array for placement and a classical PDA for active users—to ensure efficient multicast delivery.
- Different constructions like MAN-HpPDAs and t-design based HpPDAs, including MDS-coded and secretive variants, enable optimized memory-rate-subpacketization trade-offs.
Searching arXiv for the cited HpPDA and hotplug coded caching papers to ground the article and confirm metadata. Hotplug Placement Delivery Arrays (HpPDAs) are a combinatorial abstraction for centralized coded caching systems in which only a subset of users is active during the delivery phase. They generalize the classical Placement Delivery Array (PDA) formalism by separating placement structure from delivery structure: an HpPDA consists of a star-only array over all users together with a classical PDA over the active users, linked by a matching condition that must hold for every possible active subset. This construction captures the defining hotplug constraint that placement is performed without knowing which users will later be offline, while delivery must still exploit coded multicast opportunities among whichever users are active. HpPDAs were introduced for hotplug coded caching and subsequently used to derive MAN-induced and -design-based schemes, later extended with MDS-coded placement and, under information-theoretic secrecy constraints, with secret sharing, Cauchy-matrix mixing, and masking keys (Rajput et al., 2023, Chinnapadamala et al., 2024, Chinnapadamala et al., 18 Jul 2025).
1. Origin and system model
Hotplug coded caching modifies the Maddah-Ali–Niesen setting by allowing some users to be offline during delivery. In a hotplug system, a server stores files and serves users over an error-free shared link, but exactly users are active during delivery; the identities of those active users are unknown at placement time, although the value of is known (Chinnapadamala et al., 2024). Placement is centralized and demand-agnostic, and delivery must succeed for every active subset with (Rajput et al., 2023).
This model was first introduced by Ma and Tuninetti, and HpPDAs were later formulated to encode the combinatorial condition that a single placement pattern must support any realization of the active set (Chinnapadamala et al., 2024, Rajput et al., 2023). A fundamental implication of the hotplug model is that the system cannot outperform a classical coded caching problem with users, so converse bounds for the classical setting apply with 0 replaced by 1 (Chinnapadamala et al., 2024). In the secretive hotplug setting, an additional lower bound from private or secretive coded caching implies 2, so at least one file-size transmission is necessary under secrecy (Chinnapadamala et al., 18 Jul 2025).
The central design objectives are therefore threefold: robustness to unknown offline users, efficient multicast coding during delivery, and control of rate, memory, and subpacketization. HpPDAs provide a compact way to express all three.
2. Formal definition and relation to classical PDAs
A classical 3-PDA is an 4 array whose entries are either stars or integers, with exactly 5 stars in each column, every integer appearing at least once, and the standard PDA cross condition requiring that if the same integer appears twice, the corresponding 6 subarray has stars off the diagonal (Chinnapadamala et al., 18 Jul 2025). A PDA induces a classical coded caching scheme with subpacketization 7, cache ratio 8, and rate 9 (Chinnapadamala et al., 18 Jul 2025, Chinnapadamala et al., 2024).
An HpPDA replaces the single array by a pair 0. In the formulation used in the hotplug literature, 1 is an 2 array with entries either “3” or null, each column containing exactly 4 stars, while 5 is an 6 classical 7-PDA (Chinnapadamala et al., 18 Jul 2025, Chinnapadamala et al., 2024). The defining hotplug matching condition is that for every active subset 8 with 9, there exists a row subset 0 with 1 such that the subarray 2 has the same star pattern as 3 (Rajput et al., 2023).
This condition is the core of the framework. It means that once the active users are known, the server can select the corresponding rows 4, fill the null entries of 5 with the integer labels of 6, and recover a valid PDA for those active users. Delivery then proceeds exactly as in the classical PDA setting, but only on the induced subarray (Chinnapadamala et al., 2024). Offline users simply disappear from the induced delivery instance; the combinatorial structure required for decodability survives because the star pattern of 7 is guaranteed to appear inside 8 for every active set (Chinnapadamala et al., 18 Jul 2025).
The parameter mapping depends on the specific construction. In the uncoded HpPDA scheme of the original formulation, the achievable point is
9
with MDS coding across the 0 subfiles to generate 1 coded subfiles (Rajput et al., 2023). In the later MDS-coded hotplug scheme, the placement dimension is enlarged to 2, yielding
3
with operational subpacketization 4 (Chinnapadamala et al., 2024). In the secretive setting, the delivery load becomes
5
because each multicast transmission carries one coded share of size 6 (Chinnapadamala et al., 18 Jul 2025).
3. Placement and delivery mechanisms
The original HpPDA-based hotplug scheme uses an 7 MDS code across file subfiles. Each file is partitioned into 8 equal-sized subfiles and encoded into 9 coded subfiles indexed by the rows of 0; user 1 stores precisely those coded subfiles corresponding to star positions in column 2 of 3 (Rajput et al., 2023). When an active set 4 is revealed, the server chooses a row subset 5 whose star pattern over columns 6 matches 7, fills the non-star entries with the integers of 8, and for each integer 9 broadcasts the XOR of the coded subfiles indexed by entries equal to 0 (Rajput et al., 2023).
The correctness argument is inherited from the classical PDA formalism. Because 1 satisfies the PDA cross condition, every user participating in a multicast already holds the interfering coded subfiles as side information and can therefore recover its desired coded subfile from that transmission (Chinnapadamala et al., 2024). Each active user obtains 2 coded packets from delivery and already has 3 coded packets from placement; with an 4 MDS code of dimension 5, these 6 coded packets suffice to reconstruct the entire file (Chinnapadamala et al., 2024).
The later MDS-coded scheme of Rajput and Rajan retains the same HpPDA combinatorics but shifts the operating point to lower memory. For a fixed HpPDA 7, the earlier uncoded construction operates at 8, whereas the new scheme operates at 9. Since 0, it follows that
1
so the new scheme moves to a smaller memory point and improves rate behavior in lower-memory regimes relative to the prior HpPDA-based construction (Chinnapadamala et al., 2024).
A worked MAN-HpPDA example appears repeatedly in the literature: for 2, 3, and 4, the parameters are 5, 6, 7, 8, and 9 (Rajput et al., 2023, Chinnapadamala et al., 2024, Chinnapadamala et al., 18 Jul 2025). In the non-secretive MDS-coded realization, 0, so a 1 MDS code is used and the achieved point is 2 (Chinnapadamala et al., 2024). In the earlier HpPDA realization with 3, the same combinatorics yield 4 (Rajput et al., 2023). This contrast illustrates how the same HpPDA can support different caching schemes depending on the coding layer placed on top of it.
4. Principal HpPDA constructions
Two HpPDA classes are explicitly identified in the literature: MAN-HpPDAs and HpPDAs derived from 5-designs (Chinnapadamala et al., 18 Jul 2025).
MAN-HpPDAs
MAN-HpPDAs are obtained by taking the MAN PDA over 6 users as the active-user delivery array 7, and the MAN PDA over 8 users with all integer entries replaced by null as the global placement array 9 (Rajput et al., 2023). For integers 0, 1, and 2, the resulting parameters are
3
The HpPDA property follows from the combinatorial alignment of 4-subsets: for any active set of size 5, the rows corresponding to the 6-subsets of that active set provide the required star pattern (Chinnapadamala et al., 18 Jul 2025).
In the secretive setting, the MAN-HpPDA scheme achieves
7
and
8
with the special case 9 yielding 00, which is optimal under the secrecy lower bound 01 (Chinnapadamala et al., 18 Jul 2025).
HpPDAs from 02-designs
The second class is derived from a 03-04 design 05, with users indexed by points and rows indexed by blocks (Rajput et al., 2023, Chinnapadamala et al., 18 Jul 2025). The star-only array 06 is the transposed incidence matrix with “1” replaced by “07” and “0” by null, so 08, 09, and each column has 10 stars (Rajput et al., 2023). The delivery PDA 11 is assembled from rows indexed by pairs 12, where 13 is an 14-subset of 15 and 16, for chosen integers 17 satisfying 18 (Chinnapadamala et al., 18 Jul 2025).
The resulting parameters are
19
and 20 is an HpPDA for 21 (Chinnapadamala et al., 18 Jul 2025). This construction is significant because it allows more flexible parameter tuning than MAN-HpPDAs and can reduce subpacketization relative to 22 in MAN-based schemes (Chinnapadamala et al., 18 Jul 2025).
The earlier 23-scheme literature also studies rate improvement by deleting certain integer labels from 24 when 25, thereby reducing transmissions while preserving decodability (Rajput et al., 2023). For MAN-HpPDAs this yields an improved rate
26
and for the 27-design case a more general deletion formula based on layered MAN subarrays inside 28 (Rajput et al., 2023). This suggests that HpPDAs should be viewed not merely as static combinatorial objects, but as a basis for subsequent transmission-pruning mechanisms.
5. Secretive HpPDAs and information-theoretic secrecy
The paper "Secretive Hotplug Coded Caching" extends HpPDA-based hotplug systems with perfect information-theoretic secrecy (Chinnapadamala et al., 18 Jul 2025). The secrecy model assumes honest-but-curious, non-colluding users and public server transmissions. Two secrecy constraints are imposed. First, cache secrecy requires
29
so a cache alone reveals no information about any file (Chinnapadamala et al., 18 Jul 2025). Second, for each active user 30 demanding 31, decodability and delivery secrecy require
32
where 33 denotes the delivery transmissions (Chinnapadamala et al., 18 Jul 2025).
The proposed secretive schemes share several coding ingredients. Each file is split into 34 equal-size parts and encoded using a 35 non-perfect secret sharing scheme, so any set of at most 36 shares leaks no information, while 37 shares suffice to reconstruct the file (Chinnapadamala et al., 18 Jul 2025). These shares are formed by linear combinations of file parts and independent keys via a square Cauchy matrix, ensuring that every submatrix is full rank and preventing linear leakage (Chinnapadamala et al., 18 Jul 2025). The resulting 38 shares are then encoded by an 39 MDS code to produce 40 coded shares indexed by the rows of 41, and each cache stores the 42 coded shares corresponding to star positions in its column (Chinnapadamala et al., 18 Jul 2025).
Additional random vectors 43 are stored as one-time-pad keys to mask transmissions that are not useful to all active users (Chinnapadamala et al., 18 Jul 2025). In the secretive MAN-HpPDA scheme, for each 44-subset 45 of active users, the server transmits
46
and only users in 47 possess the key 48 needed to remove the mask (Chinnapadamala et al., 18 Jul 2025). In the 49-design-based secretive scheme, multicast signals indexed by subsets 50 with 51 are similarly masked, while transmissions useful to all active users, corresponding to 52, need not be masked (Chinnapadamala et al., 18 Jul 2025).
A baseline secretive scheme, adapted from the classical PDA setting of Meel–Rajan, uses a 53-PDA 54 directly and achieves memory
55
and rate 56, where the additional 57 term reflects a complete per-file key budget (Chinnapadamala et al., 18 Jul 2025). The HpPDA-based secretive schemes exploit the larger ambient 58 through the placement array 59 and outperform this baseline in specific memory ranges (Chinnapadamala et al., 18 Jul 2025).
6. Performance, complexity, and known trade-offs
The literature emphasizes that HpPDAs are primarily a mechanism for navigating the memory–rate–subpacketization trade-off under hotplug constraints. Their main benefit is structural robustness: placement is fixed once for all users, yet delivery can adapt to any active subset through the subarray matching property (Rajput et al., 2023, Chinnapadamala et al., 18 Jul 2025).
The following table summarizes the principal parameter mappings that recur across the literature.
| Construction | Achievable point | Notes |
|---|---|---|
| Original HpPDA scheme | 60 | Uses 61 MDS coding (Rajput et al., 2023) |
| MDS-coded HpPDA scheme | 62 | Extends operation to lower memory (Chinnapadamala et al., 2024) |
| Secretive HpPDA scheme | 63 | Adds non-perfect secret sharing, Cauchy mixing, masking (Chinnapadamala et al., 18 Jul 2025) |
For MAN-HpPDAs, the subpacketization 64 grows combinatorially with 65, which can be prohibitive (Chinnapadamala et al., 18 Jul 2025). This is one of the major practical limitations of the MAN family. The 66-design-based HpPDAs can have substantially smaller 67, where 68 is the number of blocks in the underlying design, and are therefore presented as a way to improve practicality while retaining good memory–rate performance (Chinnapadamala et al., 18 Jul 2025). The MDS and secret-sharing layers add further linear-algebraic complexity: MDS encoding and decoding involve finite-field operations across 69 coded packets, and the secretive schemes additionally require Cauchy-matrix-based share generation and one-time-pad key handling (Chinnapadamala et al., 18 Jul 2025).
Several numerical comparisons are reported. For 70, the secretive MAN-HpPDA scheme outperforms the secretive baseline in the low-memory region 71, with load decreasing from 72 to 73, while the secretive 74-design HpPDA scheme derived from a 75-76 design outperforms the baseline in 77, with 78 from 79 down to 80 (Chinnapadamala et al., 18 Jul 2025). For 81, the MAN-HpPDA scheme beats the baseline for 82, and the 83-design scheme from a 84-85 design beats the baseline over 86; between 87 and 88, the 89-design scheme is better than MAN-HpPDA, while below 90, MAN-HpPDA is better among the proposed schemes (Chinnapadamala et al., 18 Jul 2025).
In the non-secretive MDS-coded setting, the same pattern appears. For 91 with a 92-93 design, the points 94 and 95 improve over both the baseline and the improved 96-scheme in the memory interval from 97 to 98 file units (Chinnapadamala et al., 2024). For 99, improvement is reported from 00 with 01 to 02 with 03 (Chinnapadamala et al., 2024).
These results suggest a stable qualitative pattern: MAN-HpPDAs tend to be stronger in lower-memory regimes, while 04-design HpPDAs become competitive or superior in moderate-memory regimes, especially when reduced subpacketization is valuable (Chinnapadamala et al., 18 Jul 2025). The papers stop short of a universal dominance statement, and the observed behavior is explicitly parameter-dependent.
7. Extensions, variants, and open directions
HpPDAs have already been generalized beyond the original dedicated-cache single-access model. A 2026 extension introduces a generalized HpPDA for combinatorial multi-access hotplug networks, where each user accesses multiple caches and only a subset of caches is online during delivery (Singh et al., 15 Jan 2026). In that framework, a cache-level star array 05, a derived user-level array 06, and a family of PDAs 07 indexed by the number of online neighboring caches together replace the single pair 08 (Singh et al., 15 Jan 2026). This generalization preserves the central HpPDA principle—matching star patterns for every admissible online configuration—while broadening the topology to multi-access networks.
Several open directions are explicitly noted in the secretive hotplug literature. One is collusion: the current secrecy guarantees are for honest-but-curious, non-colluding users, and extending them to colluding sets remains open (Chinnapadamala et al., 18 Jul 2025). Another is decentralized placement: all HpPDA constructions discussed are centralized, and a decentralized hotplug analog with secrecy is not yet provided (Chinnapadamala et al., 18 Jul 2025). Heterogeneous cache sizes, joint file secrecy and demand privacy, and extensions to multi-server, combination-network, D2D, or fog-RAN settings are also identified as unresolved problems (Chinnapadamala et al., 18 Jul 2025).
A further issue is subpacketization reduction. This theme already appears in the non-secretive literature, where 09-design constructions are valued partly because they can reduce 10 relative to MAN-HpPDAs (Rajput et al., 2023, Chinnapadamala et al., 2024). The multi-access generalization continues this emphasis by allowing tunable parameters 11 that control redundancy elimination and subpacketization (Singh et al., 15 Jan 2026). A plausible implication is that future HpPDA research will focus less on introducing the abstraction itself—which is now mature—and more on exploiting it as a design template for new combinatorial families with better rate–memory–subpacketization trade-offs under richer operational constraints.
In summary, HpPDAs occupy a specific role in coded caching theory: they are the canonical combinatorial mechanism for hotplug robustness. Their importance lies not in a single scheme, but in the way they decouple global placement from active-set-specific delivery. MAN-HpPDAs and 12-design HpPDAs provide the two foundational construction classes, the MDS-coded refinement shifts achievable points to lower memory, and the secretive extension shows that the same combinatorial skeleton can support perfect information-theoretic secrecy through layered coding and masking (Rajput et al., 2023, Chinnapadamala et al., 2024, Chinnapadamala et al., 18 Jul 2025).