Function-Correcting Partition Codes (FCPCs)
- FCPCs are codes that encode functions through domain partitions, ensuring that up to t errors do not cause confusion between distinct partition blocks.
- They enable simultaneous protection for multiple functions by refining joint partitions, thereby achieving bandwidth savings and improved redundancy over independent FCCs.
- The construction leverages coset partitions, partition graphs, and block-preserving contractions to optimize redundancy while providing inherent function-class privacy.
Function-correcting partition codes (FCPCs) generalize the framework of function-correcting codes (FCCs) by encoding functions characterized not by their full specification but via partitions of the domain . A -error FCPC, also called a -encoding, maps elements from to codewords in such that symbols from distinct blocks of a chosen partition cannot be confounded by up to errors. This approach subsumes classical FCCs as the special case corresponding to partitions derived from the fibers of . Beyond unifying protection for multiple functions and enabling potential bandwidth and privacy advantages, FCPCs support constructions leveraging coset partitions, partition graphs, and block-preserving contractions for optimal or near-optimal redundancy. The structural properties of the underlying domain partitions, as well as their refinements and joins, drive the code construction, redundancy analysis, and privacy guarantees associated with FCPCs (Rajput et al., 10 Jan 2026).
1. Formal Definition and Structural Properties
Given a partition of , a -encoding is a systematic mapping
such that for any and with ,
where denotes Hamming distance. The minimum for which such a map exists is the optimal redundancy . Under this encoding, up to errors cannot result in confusion between codewords from distinct partition blocks, enforcing correct function evaluation in the presence of errors.
Any function naturally induces its domain partition
and a code is an -FCC if and only if it is a -encoding. Thus, .
2. Simultaneous Protection for Multiple Functions
To protect functions on simultaneously, FCPCs utilize the join (i.e., common refinement) of their respective domain partitions:
where each block of is an intersection . Any -encoding is automatically an -FCC for all by Lemma 1. Redundancy bounds for the join are given by
where denotes the minimum length of a -ary error-correcting code.
Two key metrics introduced are partition redundancy gain and partition rate gain:
- Partition redundancy gain per function:
- Partition rate gain:
where .
These gains quantify bandwidth savings of simultaneously protecting multiple functions compared to independent FCCs.
3. Specialization to Linear Functions and Coset Partitions
When is linear, the domain partition is the coset partition . For linear maps , their shared kernel defines a coset partition that simultaneously protects all . Specifically, any -encoding for these cosets yields a code correcting errors for all functions.
For example, taking , over gives , with four resulting cosets. The optimal code correcting errors for both functions requires redundancy 3, while applying codes separately would need redundancy 2 for each.
4. Partition Graphs, Cliques, and Redundancy Optimization
The computation of can be reduced via the notion of the partition graph . This is an -partite graph where each vertex is a vector in and edges connect , () whenever their distance realizes the minimal inter-block distance. A full-size clique is a selection of one representative from each block with all inter-block distances minimized.
If forms such a clique, the problem reduces to constructing a code for the partition distance matrix . Theorem 13 shows this achieves precisely.
The following table summarizes full-size clique existence for notable partitions:
| Partition Type | Clique Construction | Clique Size |
|---|---|---|
| Weight partition | ||
| Support partition | with on |
Here, is fixed.
5. Block-Preserving Contractions and Generalization beyond Cliques
If admits no full-size clique, block-preserving contractions are employed. A block-preserving contraction consists of a subset and a map such that when and from distinct blocks,
Theorem 20 proves that restricting to allows calculation of . This reduction may dramatically decrease the code design complexity.
For instance, a 3-block partition of with no 3-clique can be contracted onto a of size 4 while preserving necessary distance properties.
6. Partial Privacy and Function-Class Privacy
FCPCs deliver partial privacy: the transmitter learns only the domain partition , not the function specifics. Therefore, the transmitter cannot distinguish which among all those inducing is protected, and only the function class is revealed. The number of such functions for finite is . This property—labelled in the original work as function-class privacy—applies to both linear and nonlinear functions.
For example, a 4-block partition of corresponds to multiple linear maps as well as many nonlinear functions, all equally protected by the same FCPC without exposing which function is in use.
7. Significance, Applications, and Broader Implications
FCPCs generalize and unify error-correcting code design for functional data and facilitate simultaneous correction for multiple functions with potential bandwidth savings as quantified by partition redundancy and rate gain. Their framework naturally extends classical coset constructions and incorporates combinatorial optimization via partition graphs and contractions. Notably, FCPCs' partial privacy is intrinsic and does not rely on cryptographic assumptions, distinguishing functional privacy at the partition level in coding-theoretic contexts (Rajput et al., 10 Jan 2026).