1. Introduction
Internet of Things (IoT) infrastructures continuously collect fine-grained sensing streams from smartphones, wearables, smart buildings, industrial equipment, and environmental networks. Differential privacy (DP) limits the change in an output distribution when the dataset changes according to a declared neighboring relation [
1,
2]. The definition does not assume that records are statistically independent. The practical difficulty in correlated sensing is instead that a component-level or time-point-level relation may be narrower than the user, event, or dependency neighborhood that an application intends to protect. Correlated observations can also retain predictive information about an attribute without violating the stated DP inequality.
This paper calls the latter phenomenon correlation-assisted inference. Indoor light and CO
2 jointly indicate occupancy, accelerometer and gyroscope features jointly describe motion, and nearby motes observe similar environmental trends. Pufferfish makes the protected secrets, discriminative pairs, and data-generating assumptions explicit [
3,
4]; Blowfish specifies protected distinctions through a policy graph [
5]; and temporal analyses show how repeated releases interact with temporal dependence [
6,
7]. These results motivate an IoT mechanism whose formal privacy unit is explicit and whose empirical calibration recognizes cross-channel and lagged structure.
Dependence-aware DP, Bayesian DP, correlated DP, and dependent-tuple analyses formalize related concerns under different models [
8,
9,
10]. Workload mechanisms and streaming mechanisms solve different release problems: the matrix mechanism optimizes a fixed linear workload [
11], CTS-DP publishes correlated time series [
12], and CGM uses temporally correlated Gaussian noise under
-local DP [
13]. GC-DP instead targets the central release of multichannel, window-level representations. These methods are not interchangeable baselines unless the privacy unit, trust model, value of
, workload, and release schedule are matched.
GC-DP represents sensing components by a weighted calibration graph and distinguishes it from the fixed policy graph that declares adjacency. Weighted degree is an allocation surrogate, not a formal leakage bound. A certified sensitivity is derived for every released coordinate , and a graph-expanded empirical influence may only increase the calibrated scale . Local budgets are computed from exposure, influence, and validation utility while satisfying . The release is .
The practical contribution is the integration of lag-aware dependency estimation, conservative sensitivity certification, and risk–utility allocation in one IoT release pipeline. Absolute lagged Pearson correlation was selected because it is bounded, sign-invariant, interpretable, and computable in time; thresholding and a degree cap produce an auditable sparse graph. Compression reduces redundant empirical scores but never reduces the certified bound. These choices are pragmatic rather than universally optimal; mutual information, partial correlation, or domain graphs may be substituted when their calibration and sensitivity are specified. When graph or utility statistics use protected records, GC-DP assigns budgets , , , and to their release, with and total cost .
The evaluation uses UCI-HAR, WISDM, Occupancy Detection, and Intel Lab Data. The experimental implementation follows Algorithms 1–4: it applies the fixed component-occurrence adjacency, includes the certified coordinatewise sensitivity floor, and then uses graph exposure, empirical influence, and validation utility to allocate the release budget. The tables report higher utility and lower attribute-inference AUC for GC-DP than for Lap-DP, Gau-DP, Ada-DP, and Risk-DP. These comparisons concern the matched central-release implementations evaluated here; mechanisms with different secret definitions, trust models, workloads, values of , or release schedules remain scope comparisons rather than numerical baselines.
The contributions are as follows: (1) a query-independent graph-expanded adjacency that states the protected component-level neighborhood; (2) a separation between certified global sensitivity and empirical graph influence; (3) an explicit public/private calibration boundary and composed privacy accounting; and (4) an empirical evaluation of utility, attribute inference, ablations, and computational cost on four public IoT sensing datasets.
The remainder of this paper is organized as follows.
Section 2 reviews differential privacy for IoT data analytics, correlation-aware privacy, and graph-structured budget allocation.
Section 3 introduces the notation, IoT stream model, differential privacy background, and graph-based privacy–utility objective.
Section 4 presents the GC-DP framework, including correlation graph construction, graph-calibrated sensitivity estimation, adaptive budget allocation, and the complete private release mechanism.
Section 5 reports the experimental settings, utility comparison, privacy leakage analysis, ablation study, and runtime evaluation.
Section 6 concludes the paper.
| Algorithm 1 Data-Driven Correlation Graph Construction |
Require: Public or privately calibrated bounded data/score vector, L, , , degree cap K, smoothing coefficient Ensure: Calibration graph , normalized adjacency matrix , graph exposure vector - 1:
Apply fixed bounded normalization parameters. - 2:
Obtain from public normalized data or read the already released private score vector ; do not access protected calibration records again. - 3:
Form undirected candidates and sort them by decreasing with a lexicographic tie break. - 4:
Initialize . In sorted order, accept only if and , then set . - 5:
Compute ; use zero inverse degree for isolated nodes. - 6:
Compute direct weighted degree for each node . - 7:
Compute smoothed exposure score . - 8:
Normalize into for all m. - 9:
return , , and
|
| Algorithm 2 Graph-Calibrated Sensitivity Estimation |
Require: Query q, fixed adjacency , certified bounds , calibrated graph , exposure , public/private calibration data, Ensure: Certified bounds , empirical scores , release numerators - 1:
for each released coordinate k do - 2:
Verify analytically that ; otherwise use the clipped range . - 3:
On public calibration data, compute the bounded mask score using fixed and ; in private mode, read the released coordinate of without accessing protected records again. - 4:
Inflate and cap the public empirical score, or project the private score, to obtain . - 5:
Set . - 6:
end for - 7:
return
|
| Algorithm 3 Utility-Guided Adaptive Privacy Budget Allocation |
Require: , calibrated , , , , Ensure: - 1:
Verify that . - 2:
for each output coordinate k do - 3:
Compute from , then and . - 4:
Set . - 5:
end for - 6:
Set . - 7:
return
|
| Algorithm 4 Graph-Calibrated Differential Privacy Mechanism |
Require: Protected data , query q, fixed adjacency , release budget , fixed/public or -DP parameter object Ensure: Privatized analytics output - 1:
Verify , , and for every possible . - 2:
for each released coordinate do - 3:
Set and . - 4:
Sample independently and release . - 5:
end for - 6:
return
|
3. Preliminaries
This section distinguishes the declared privacy unit, fixed policy adjacency, learned calibration graph, input-node index, and output-coordinate index.
Table 1 summarizes the notation.
3.1. IoT Sensing Streams and Analytics Queries
Let contain clipped multivariate observations. Before calibration, the controller fixes atomic occurrence-level units and their domains. A graph node is a component type, whereas an atomic unit is that component’s occurrence in record or window t; the two are not interchangeable. The experiments protect a supplied feature-window coordinate for UCI-HAR, a sensor-axis contribution within one WISDM window, a time-stamped channel value for Occupancy Detection, and a mote–channel contribution within one Intel Lab window. The guarantee is component-occurrence privacy, not user-level or device-level privacy. User- or device-level protection requires grouping all corresponding occurrences into one adjacency and generally has a larger sensitivity.
The released query is , with coordinate distinguished from input-node index i. Aggregate queries and clipped feature representations are both covered. A deterministic projection maps coordinate k to its fixed interval before randomization.
Let be a predeclared expansion set obtained from a public policy graph or a specification independent of the protected data, where is one atomic occurrence. Datasets satisfy when, for one u, they agree outside and may differ arbitrarily within the fixed clipped domains inside that set. The conventional component-replacement relation is recovered when . The relation is defined on input occurrences and does not depend on the query, observed displacement, or learned sensitivity. Raw-channel, temporal-segment, and feature-level graphs are separate instantiations and are not mixed within one run. In the benchmark experiments, and its occurrence-level expansions are fixed from the public data specification before calibration; the learned weighted graph is used only for sensitivity inflation and budget allocation.
3.2. Differential Privacy Under Correlated Observations
A randomized mechanism is -DP under if for every and measurable . The guarantee limits distinguishability for exactly those pairs. It does not state that an attribute is unrecoverable from correlations, nor does it automatically extend component-record privacy to a whole user or device.
Correlation-assisted attribute inference is evaluated separately from the formal guarantee. A lower attack AUC or F1 indicates weaker performance for the evaluated adversary, not absence of privacy risk. This distinction also explains why graph-weighted degree can guide allocation without being presented as a theorem-level measure of leakage.
3.3. Correlation Graph and Privacy–Utility Objective
The calibration graph has M nodes and bounded weights . Its node representation is fixed for each experiment. The graph ranks empirical dependence for budget allocation; the independent policy graph defines adjacency. The two coincide only when is constructed entirely from public information and explicitly adopted as policy before the protected release data are observed.
The normalized degree score is treated as an interpretable exposure surrogate. It is neither equal to nor an upper bound on privacy loss, mutual information, reconstruction success, or attack AUC. The ablation and attribute-inference experiments evaluate its empirical contribution, while the certified sensitivity bound remains the basis of the formal guarantee.
GC-DP distributes a release budget so that . Exposure and certified sensitivity decrease a coordinate’s allocation weight, while bounded validation utility increases it. If any of these quantities is obtained from protected records, its private calibration is included in before the allocation is used.
4. Methodology
4.1. Data-Driven Correlation Graph Construction
GC-DP constructs a bounded calibration graph over the node representation fixed for the task. The graph ranks synchronous and lagged empirical dependence for allocation; it does not itself define privacy loss. Calibration and protected release are separate stages, and every calibration quantity is either independent of the protected records or released under an explicit calibration budget.
Let the calibration matrix contain bounded observations of M fixed nodes. Public medians and interquartile ranges may be used for robust normalization. If these statistics are computed from protected records, their release is included in the parameter object and budgeted; computing them first and then treating them as constants is not sufficient. Fixed physical ranges or public training statistics are preferred because they make clipping and sensitivity auditable.
For nodes i and j, let be the absolute Pearson correlation at lag ℓ after fixed bounded preprocessing. Set when fewer than two aligned pairs remain or either aligned series has zero variance. The bounded score is . After calibration, when and zero otherwise. Absolute lagged correlation was selected because it is bounded, sign-invariant, inexpensive, and directly inspectable. It does not distinguish direct from mediated dependence, so partial correlation, mutual information, or a domain graph may be preferable when supported by the application and privacy accounting.
Thresholding first forms the undirected candidate set . Candidates are sorted by decreasing , with lexicographic node order used as a deterministic tie-breaker. Starting from an empty undirected graph, an edge is accepted only when both current endpoint degrees are strictly smaller than K. This greedy symmetric rule guarantees for every node; it does not reinstate sub-threshold neighbors, and isolated nodes are permitted. The accepted edge receives . Then , with inverse-degree entries defined as zero for isolated nodes. The construction limits weak or spurious links while preserving an auditable sparse structure; it is a deterministic sparsification heuristic, not an optimality claim.
The allocation surrogate uses and . If , min–max normalization gives ; otherwise, set every . It ranks direct and one-hop graph exposure. No formal equivalence between weighted degree and DP leakage is assumed; the attack evaluation tests only whether the surrogate improves resistance for the specified empirical adversary.
Algorithm 1 receives an already public or privately released score vector and applies only post-processing. It returns , , and .
Direct computation over pairs, lags, and aligned observations costs time. Thresholding and per-node ranking cost time; the dense scores require memory beyond the input. FFT-based correlation can reduce the lag term for long streams, but the reported implementation uses direct correlation.
4.2. Public and Private Calibration
Collect all release-dependent parameters in . In public-calibration mode, , clipping bounds, and tuning choices use only public information independent of the protected records. A historical or validation split is not automatically public; if it contains protected units, it must be included in the accounting.
In private-calibration mode, fixed preprocessing maps the pairwise scores to a vector . Define . GC-DP releases with independent . The universal bound is valid because every coordinate is in ; a tighter value may be used only when proved for the stated score and adjacency. Thresholding, degree capping, normalization, compression, and exposure scoring are post-processing. For utility and empirical-influence vectors , define for . Independent coordinatewise Laplace noise with scales and , followed by projection to , releases these vectors; the universal bounds are .
If protected validation utility selects from a finite set , the exponential mechanism samples t with probability proportional to , where . The calibration budget is . Clipping and normalization parameters must remain public/fixed or be included in a separately specified DP parameter release; they cannot redefine adjacency. Private graph calibration can be noisy under the universal bound, which is an explicit utility limitation rather than an unaccounted guarantee.
4.3. Graph-Calibrated Sensitivity Estimation
Let
. For the fixed relation
, the true sensitivity of output coordinate
k is
A certificate must satisfy . Counts, fixed-size means, and histograms use analytic bounds from the declared adjacency and ranges. For an arbitrary extractor clipped to , is always valid, although potentially loose. The vector query obeys ; in general, the maximum coordinate bound is not an ℓ1 vector-sensitivity bound.
Bounded leave-one-node masking measures observed task influence, not global sensitivity. Fix a mapping
from every output coordinate to its associated graph nodes; when
,
. Let
, where
applies the prespecified mask to node type
. For a fixed compressed set
, define
The set
retains one representative from a pair with normalized similarity at least
, choosing the representative with greater exposure and using a fixed node-index tie break. This formula is evaluated on public calibration data; with protected calibration data, Algorithm 2 consumes the already released private vector
from
Section 4.2 rather than remasking protected records. Inflation by
and clipping at
stabilize this empirical score, but no finite
converts a validation maximum into a worst-case certificate. Compression and clipping therefore affect only
. The release uses
so empirical estimation error cannot lower the certified bound. The analytic route is used whenever the query algebra and adjacency yield a closed-form global bound; bounded perturbation is used only to rank influence for allocation or conservatively increase
.
This separation explains the practical role of graph expansion and compression. Expansion directs more noise or less budget toward coordinates linked to influential nodes, whereas compression avoids repeatedly counting nearly collinear evidence in the empirical score. Neither operation is claimed to be optimal, and neither is allowed to reduce formal sensitivity.
Proposition 1. For every coordinate k, . Thus, is a valid coordinatewise sensitivity bound. Graph compression, masking error, and the choices of γ, , κ, and may change utility and empirical attack behavior but cannot invalidate this inequality because the independently certified term remains at the maximum.
4.4. Utility-Guided Adaptive Privacy Budget Allocation
The certified scale numerators protect the declared adjacency. GC-DP then allocates across coordinates to trade task utility against empirical graph exposure without changing those certificates.
Let be the budget for output coordinate k, with . The bounded utility score is the normalized reduction in validation utility when the associated node or feature group is masked; aggregates use a bounded contribution score. The score and resulting allocation are privacy-dependent. They must be computed from public information or released within . A non-private allocation computed from the protected release data is outside Theorem 1.
Using the fixed coordinate–node map
from
Section 4.3, define coordinate exposure by
Let , , and . Larger reduces the allocated budget and increases noise; larger preserves task-critical coordinates. The exponents , , and control the three effects.
With
, allocation is
The floor prevents numerical degeneracy and the normalization makes the total budget exactly .
When , graph exposure does not affect allocation, giving the utility-only Ada-DP reduction; when , validation utility does not affect it, giving the exposure-only Risk-DP reduction. The rule is a transparent allocation heuristic rather than the solution of a universal optimality criterion.
Algorithm 3 is the post-processing of the fixed or privately calibrated object and requires time and memory.
Proposition 2. Algorithm 3 guarantees and . This follows immediately from positivity of and summing the normalized fractions.
4.5. Complete Graph-Calibrated Private Release Mechanism
The release stage accepts a fixed or privately calibrated parameter object
; it does not recompute graph, threshold, empirical influence, utility, clipping, or allocation statistics from the unprotected release data. For
, it releases
where
and
. The graph may increase
or decrease
, but it cannot lower the certified bound.
Theorem 1. Fix independently of the protected data. Suppose that for every feasible fixed calibration output θ, each nonconstant coordinate has , , , and ; a coordinate with zero sensitivity is released deterministically. Then the release kernel defined by Algorithm 4 is -DP under for every such fixed θ. If an -DP calibration kernel C produces θ from the same protected records under the same relation, the joint adaptive procedure , and hence its released marginal, is -DP.
Proof. For fixed
and any
, independence of the Laplace variables gives
Integration gives the same inequality for measurable output sets for every fixed feasible . Multiplying the measure bound for C by the uniform kernel bound for and integrating over proves the joint and marginal guarantee. ☐
A graph learned from sensitive data may tune , but it cannot redefine adjacency after the data are observed. Reusing an already released is post-processing; generating fresh releases from the same protected units incurs composition. A downstream model conducts post-processing only when it receives no additional raw protected data.
The theorem covers one invocation of q over the declared dataset. Disjoint occurrence sets may use parallel composition only when the fixed adjacency cannot change more than one set; overlapping windows, repeated release of the same occurrence, or a release of an entire test matrix requires sequential or appropriate continual-observation accounting. Each benchmark result below evaluates one declared release invocation at the displayed budget. The empirical comparison does not claim a continual-observation guarantee for an indefinitely repeated stream; such a deployment must compose repeated accesses separately.
5. Experiments
5.1. Experimental Settings
The evaluation uses four public benchmarks covering wearable activity recognition, room occupancy, and distributed environmental sensing.
Table 2 identifies the source, task, graph nodes, and exact component-record unit protected in each experiment [
25,
26,
27,
28,
29,
30,
31]. None of the reported guarantees is user-level or device-level DP.
Figure 1 separates calibration from protected release. A benchmark run has
only when its graph, clipping, utility scores, and tuning use information that is public and independent of the protected release records. Public availability of a dataset does not by itself establish this separation for a deployment. When calibration records belong to the protected population,
Section 4.2 applies and the reported cost is
.
All preprocessing, partitioning, clipping, and calibration choices are fixed before the private mechanisms are compared and are reused unchanged across methods and privacy budgets. Invalid timestamps, duplicate entries, and readings outside the physical sensor domain are removed. Short internal gaps are linearly interpolated, and longer incomplete segments are excluded before window formation. Normalization and clipping parameters are fitted only on the calibration/training portion and then frozen. Dataset-provided windows and partitions are retained where available; otherwise, a fixed partition is created before windowing so that no window crosses a split boundary.
Table 3 summarizes the dataset-specific representation and the invariants enforced by the implementation.
For UCI-HAR, WISDM, and Occupancy Detection, the same fixed lightweight classifier, training procedure, hyperparameters, and class weighting are used for every privacy mechanism; only the privatized representation changes. For Intel Lab Data, anomaly labels and thresholds are generated once from robust deviations in temperature, humidity, light, and voltage and are held fixed for all methods. Aggregate monitoring utility is normalized mean absolute error, using the fixed clipped range of the evaluated channel as the normalization constant. This controlled design prevents downstream-model retuning from confounding the comparison of privacy mechanisms.
Table 4 defines the included mechanisms. Lap-DP, Ada-DP, Risk-DP, and GC-DP are central pure-
releases and use the same coordinate certificates and total release budget. Gau-DP is an approximate-DP perturbation comparator calibrated with the analytic Gaussian mechanism [
32]; its fixed
,
ℓ2 certificate, and calibration rule are held constant across its runs. Because pure and approximate DP are different guarantees, Gau-DP is reported for empirical context and is not described as privacy-identical to the pure-
mechanisms.
Table 5 reports the fixed constants used in the experiments. The sparsification threshold
is selected once by validation F1 at
from the displayed grid;
Table 6 shows the complete sweep. Test attack AUC is not part of this rule. The benchmark evaluation uses public calibration mode, so
and the displayed
is the complete release cost for one invocation. In deployments where validation or calibration records are protected, the mechanisms in
Section 4.2 replace direct calibration and the total cost is
.
Every result in
Table 6,
Table 7,
Table 8,
Table 9,
Table 10,
Table 11 and
Table 12 is an empirical measurement from the certificate-aware implementation in Algorithms 1–4. For each dataset and budget, ten independent noise draws are evaluated with the same preprocessed data, fixed graph policy, certified bounds, allocation configuration, classifier, and attack protocol; the tables report their arithmetic means. The clipped-range certificate
is used whenever no tighter analytic certificate is available, so empirical masking never substitutes for global sensitivity. The numerical comparisons are statements about the tested configurations and are not claims of universal dominance or zero inference risk. Pufferfish, Blowfish, the matrix mechanism, CTS-DP, and CGM are discussed in
Section 2 but are not experimental comparators because their secret definitions, workloads, trust models, or release schedules are not matched to this benchmark pipeline.
Together,
Figure 1 and
Table 2,
Table 3,
Table 4 and
Table 5 connect the formal mechanism to the benchmark implementation and define the scope in which the following empirical comparisons are interpreted.
5.2. Overall Utility Under Different Privacy Budgets
Table 7 reports mean macro-F1 for UCI-HAR and WISDM. At
, GC-DP achieves a UCI-HAR F1 score of
, which is 5.4, 4.9, 2.8, and 2.1 percentage points above Lap-DP, Gau-DP, Ada-DP, and Risk-DP, respectively. Its WISDM mean is
, versus
and
for Lap-DP and Risk-DP, respectively. These are absolute percentage-point differences for the evaluated certificate-aware implementations; no statistical-significance claim is made from the rounded means alone.
Table 12.
Average runtime and peak process memory for one calibration-and-release pass at in the common evaluation environment.
Table 12.
Average runtime and peak process memory for one calibration-and-release pass at in the common evaluation environment.
| Dataset | Metric | Lap-DP | Ada-DP | Risk-DP | GC-DP | GC-DP-Cache |
|---|
| UCI-HAR | Runtime (s) | 0.08 | 0.19 | 0.42 | 0.71 | 0.24 |
| UCI-HAR | Memory (MB) | 18.4 | 23.7 | 31.2 | 35.8 | 28.6 |
| WISDM | Runtime (s) | 0.15 | 0.36 | 1.04 | 2.18 | 0.69 |
| WISDM | Memory (MB) | 24.1 | 33.5 | 48.7 | 57.4 | 42.9 |
| Occupancy Detection | Runtime (s) | 0.04 | 0.11 | 0.23 | 0.39 | 0.14 |
| Occupancy Detection | Memory (MB) | 9.8 | 13.2 | 18.5 | 21.7 | 16.1 |
| Intel Lab Data | Runtime (s) | 0.18 | 0.41 | 1.28 | 2.46 | 0.77 |
| Intel Lab Data | Memory (MB) | 27.6 | 36.9 | 52.8 | 61.3 | 45.5 |
Figure 2 visualizes the UCI-HAR means from
Table 7. All methods improve as
increases because perturbation decreases, and GC-DP has the highest mean at each tested budget. The comparison among the pure-
mechanisms uses the same certified coordinate bounds and total release budget; Gau-DP remains an approximate-DP empirical comparator.
Table 8 gives mean F1 for Occupancy Detection and Intel Lab Data. At
, GC-DP reaches 94.2%, 5.0 percentage points above Lap-DP. For Intel Lab Data, GC-DP achieves 86.7% at
and 91.3% at
. Because preprocessing, downstream models, and noise-draw counts are controlled across methods, these differences measure the effect of the evaluated perturbation and allocation rules within this benchmark.
Figure 3 reports Intel Lab aggregate normalized mean absolute error. At
, the means are
for GC-DP and
for Lap-DP. Error is normalized by the fixed clipped channel range, and the same aggregation query and data partition are used for every method.
Across
Table 7 and
Table 8 and
Figure 2 and
Figure 3, certificate-aware GC-DP has the most favorable mean utility among the evaluated private methods. The result supports the proposed allocation rule for the tested component-occurrence releases, while not implying superiority for different datasets, privacy units, or continual-release settings.
5.3. Privacy Leakage and Correlation Robustness Analysis
The attribute-inference evaluation is distinct from the formal DP adversary. For each dataset, one protected-attribute definition and one attacker configuration are fixed before the mechanism and privacy-budget sweep. The attacker observes the privatized representation produced by the evaluated mechanism and attempts to predict the protected attribute. The attack data partitions, feature map, model configuration, class weighting, thresholding rule, and score direction are identical across all compared mechanisms. AUC is oriented so that values above 0.5 denote better-than-random prediction; because an attacker may invert its score, the effective AUC is interpreted as
[
33,
34]. Lower-oriented AUC and F1 therefore mean weaker performance for this fixed attacker, not the absence of every possible inference attack.
Table 9 reports mean performance of the fixed attacker at
. GC-DP is lowest among the evaluated methods: its AUC is 0.603, 0.621, 0.637, and 0.652 on UCI-HAR, WISDM, Occupancy, and Intel Lab, respectively. These results establish lower performance for the specified attacker under the tested release protocol; they do not establish impossibility of reconstruction or resistance to attackers outside the evaluated threat model.
Table 10 gives the mean oriented attack AUCs across release budgets. The means rise with
as every mechanism adds less noise, and GC-DP is lowest at every tabulated setting. The consistent trend supports improved resistance to the specified attribute-inference attack, while remaining an empirical result rather than an extension of the formal DP theorem.
Figure 4 visualizes the Occupancy and Intel Lab means in
Table 10. With the attacker, data partition, and certified release implementation held fixed, the separation among curves measures how much usable attribute signal remains after each perturbation and allocation rule.
The sparsification threshold
is selected by validation F1 at
from the displayed grid. The selected values coincide with the maximum validation-F1 entries in
Table 6; attack AUC is not part of the selection rule. Ties are resolved in favor of the smaller threshold before test evaluation. A smaller threshold generally admits more candidate edges, although the actual density is also constrained by the symmetric degree cap.
Figure 5 plots the WISDM and Intel Lab test F1 and oriented attack AUC obtained after applying each candidate
in the fixed pipeline. It is a threshold-sensitivity analysis, not a reconstruction-error or membership-inference experiment and not a plot against measured edge density.
Table 6,
Table 9 and
Table 10 and
Figure 4 and
Figure 5 show that certificate-aware GC-DP leaves a less usable signal for the fixed attribute-inference attacker than the included baselines. This empirical result complements rather than strengthens Theorem 1, whose guarantee depends only on the declared adjacency, certified bounds, and privacy accounting.
5.4. Ablation, Runtime, and Edge Feasibility Analysis
Table 11 reports four component removals at
. Every variant retains the certified sensitivity floor and changes only the indicated empirical calibration or allocation term. The full GC-DP configuration has the highest F1 for every dataset and is Pareto-nondominated in the displayed F1–AUC space, although it is not the unique Pareto point: removing utility or compression sometimes lowers attack AUC at the cost of task F1.
Figure 6 makes the Pareto interpretation explicit. Removing utility moves it left and down: attack performance falls, but so does task F1. Removing graph exposure raises attack AUC and lowers F1. The ablation supports complementary empirical roles for the two terms without defining an arbitrary combined scalar metric.
Graph construction dominates the
calibration cost; allocation and release are linear in
d.
Table 12 reports average runtime and peak process memory for one graph-calibration-and-release pass at
. All methods use the same processed input and are evaluated in the same software and hardware environment. GC-DP incurs additional calibration cost relative to uniform and partially adaptive releases, whereas GC-DP-Cache avoids rebuilding the graph and is therefore substantially cheaper. The absolute values characterize the reported environment; the relative ordering is the relevant deployment comparison.
GC-DP-Cache reuses
before release.
Figure 7 shows the measured scaling trend as
M increases in the same evaluation environment. Cache reuse is valid only while a predeclared drift monitor accepts the graph. A public or privately released correlation summary can trigger refresh when its distance from the calibration summary exceeds a fixed threshold; periodic refresh is a fallback. Staleness does not invalidate DP when adjacency and certified bounds remain fixed, but it can degrade allocation utility and empirical inference resistance. Every refresh from protected records consumes a new calibration budget by composition [
35]. The results show that calibration dominates cost and that cached release reduces it across all tested graph sizes.
Table 11 and
Table 12,
Figure 6 and
Figure 7 indicate complementary ablation trade-offs and calibration-dominated cost.
5.5. Limitations and Scope
GC-DP has five principal limitations. First, a misspecified or stale calibration graph can misallocate budget and weaken empirical attack resistance, although certified sensitivity under fixed adjacency remains valid. Second, the universal private-graph sensitivity bound can add substantial calibration noise; the benchmark results use public calibration and therefore do not quantify that private-calibration utility cost. Third, empirical masking, graph compression, and weighted degree are allocation heuristics rather than formal leakage bounds. Fourth, GC-DP offers little advantage when dependencies are weak, the query already has a tight low-dimensional sensitivity, calibration cost dominates the release rate, or correlations change faster than they can be privately refreshed. Fifth, lower AUC/F1 for the specified attribute-inference attacker does not imply resistance to reconstruction, membership inference, or every adaptive adversary.
The included baselines share the central-release pipeline but do not cover every correlated-data framework. Pufferfish and Blowfish require a secret/policy specification; the matrix mechanism requires a linear workload; CTS-DP assumes time-series publication; and CGM uses -local DP. Matched experiments would be needed before making empirical claims against them. Future evaluation should additionally report private-calibration budget sweeps, confidence intervals from preserved run-level outputs, learned-graph diagnostics, reconstruction and membership-inference attacks, and continual-release accounting.