Papers
Topics
Authors
Recent
Search
2000 character limit reached

PEUCS: Utility Co-occurrence Structure

Updated 12 July 2026
  • PEUCS is a pairwise aggregation structure that compactly stores a 5-tuple of utility and periodicity statistics for item pairs.
  • It combines positive and negative utilities while recording modified transaction-weighted utility, periodic gaps, and support to aid effective pruning.
  • PEUCS underpins the PCUD strategy within the TPU algorithm, enabling aggressive threshold raising and reducing the cost of subsequent utility-list joins.

Searching arXiv for the specified paper and closely related periodic high-utility pattern mining work. Period-estimated Utility Co-occurrence Structure (PEUCS) is a pairwise aggregation structure introduced in "Discovering Top-k Periodic and High-Utility Patterns" for top-kk periodic high-utility pattern mining under positive and negative utilities (Zhou et al., 19 Sep 2025). In that setting, PEUCS is used alongside positive and negative utility lists (PNUL) to store 2-item co-occurrence information needed for threshold raising and pruning. For each ordered pair xyx \prec y, it records redefined transaction-weighted utility, pairwise utility, periodicity bounds, and support in a compact 5-tuple. Within the TPU algorithm, PEUCS serves as the basis for the periodic co-occurrence utility descending (PCUD) threshold-raising strategy, and more broadly supports efficient discovery of the most significant top-kk periodic and high-utility patterns, including cases with negative utility values (Zhou et al., 19 Sep 2025).

1. Formal definition

Let II be the set of all items, and let DD be a transaction database in which each transaction TkT_k has identifier tidk\mathrm{tid}_k and contains a subset of II. Each item xTkx \in T_k carries an internal utility iu(x,Tk)\mathrm{iu}(x,T_k) and an external utility xyx \prec y0. The utility of an item in a transaction is defined as

xyx \prec y1

and for an item pair xyx \prec y2 appearing in xyx \prec y3,

xyx \prec y4

The redefined transaction utility for a transaction is

xyx \prec y5

and the redefined transaction-weighted utility for a pair is

xyx \prec y6

If xyx \prec y7 denotes the multiset of adjacent-tid differences between consecutive transactions containing both xyx \prec y8 and xyx \prec y9, with kk0 and kk1, then the associated periodic statistics are:

kk2

kk3

kk4

Over all transactions, the global pair utility is

kk5

PEUCS is then defined as follows: for each ordered pair kk6, the entry kk7 is the 5-tuple

kk8

(Zhou et al., 19 Sep 2025).

This definition situates PEUCS as a pair-level summary structure rather than a list-based vertical representation. It is designed to capture utility and periodicity simultaneously, allowing subsequent threshold raising to be performed directly from precomputed pair statistics.

2. Internal layout and stored quantities

PEUCS is described as a global, in-memory, symmetric matrix in which only entries with kk9 are stored (Zhou et al., 19 Sep 2025). Each such entry aggregates, over all transactions in one pass, the following quantities:

Component Meaning
II0 Sum of II1 over all transactions containing II2
II3 Sum of II4 over all transactions containing the pair
II5 Support count of the pair
II6 Minimum periodic gap, computed on-the-fly
II7 Maximum periodic gap, computed on-the-fly

The structure is paired with PNUL, the Positive/Negative Utility List. For any itemset II8, PNUL stores tuples of the form II9, where DD0 is the positive utility of DD1 in the transaction, DD2 is the negative utility of DD3 in the transaction, and DD4 is the remaining positive utility of items DD5 in that transaction (Zhou et al., 19 Sep 2025). PNUL is used to build higher-order utility lists, whereas PEUCS stores 2-item aggregate information.

A notable design choice is that positive and negative utilities are folded into DD6, while DD7 always uses only positive-part sums (Zhou et al., 19 Sep 2025). This division allows PEUCS to accommodate negative utility values without altering the upper-bound behavior of DD8.

This layout suggests that PEUCS is intended not as a general-purpose itemset repository, but as a specialized pairwise synopsis optimized for rapid threshold adjustment before or during deeper search.

3. Construction from the transaction database

PEUCS is built by a single scan of the database (Zhou et al., 19 Sep 2025). In a transaction DD9 with identifier TkT_k0, let

TkT_k1

be the items of TkT_k2 sorted by the chosen total order. For every pair of positions TkT_k3, the algorithm considers TkT_k4 and updates the corresponding entry.

If no entry exists, it is initialized with:

  • TkT_k5
  • TkT_k6
  • TkT_k7
  • TkT_k8
  • TkT_k9
  • tidk\mathrm{tid}_k0

The updates are then:

  • tidk\mathrm{tid}_k1
  • tidk\mathrm{tid}_k2
  • tidk\mathrm{tid}_k3

If tidk\mathrm{tid}_k4, then:

  • if tidk\mathrm{tid}_k5, set tidk\mathrm{tid}_k6
  • set tidk\mathrm{tid}_k7

Otherwise, for the first occurrence:

  • set tidk\mathrm{tid}_k8

Finally:

  • tidk\mathrm{tid}_k9
  • II0

The paper provides the following pseudocode for buildPEUCS (Zhou et al., 19 Sep 2025):

xyx \prec y53

Because construction is pairwise within each transaction, the structure is sensitive to transaction length rather than only database size. That property is reflected directly in the complexity bounds reported for PEUCS.

4. Function within threshold-raising strategies

PEUCS is integrated into the TPU algorithm through three threshold-raising strategies: periodic real item utility (PIU), periodic co-occurrence utility descending (PCUD), and periodic real utility (PRU) (Zhou et al., 19 Sep 2025). Of these, PEUCS is directly central to PCUD.

PIU operates after the first scan, when for each single item II1 one knows its total utility II2 and its periodic measures II3. The set

II4

is sorted descending, and if II5, with II6 the desired number of patterns, then II7 is set to the II8-th largest value:

II9

This strategy does not require PEUCS, but establishes an initial threshold that conditions later pair filtering.

PCUD is the PEUCS-driven stage. Once PEUCS is built, all pairs xTkx \in T_k0 are collected for which xTkx \in T_k1 and the pair satisfies periodic constraints jointly. For each such pair, its utility xTkx \in T_k2 is recorded. If

xTkx \in T_k3

is sorted descending and xTkx \in T_k4, with xTkx \in T_k5 the xTkx \in T_k6-th largest value, then

xTkx \in T_k7

Because PEUCS already provides xTkx \in T_k8 for every pair, this lookup is reported as xTkx \in T_k9 where iu(x,Tk)\mathrm{iu}(x,T_k)0 after single-item pruning (Zhou et al., 19 Sep 2025). The paper explicitly notes that, in practice, PEUCS allows PCUD to be computed in one pass over iu(x,Tk)\mathrm{iu}(x,T_k)1 entries instead of repeatedly joining utility lists.

PRU is used during the depth-first search. A min-heap of size at most iu(x,Tk)\mathrm{iu}(x,T_k)2 stores discovered periodic high-utility itemsets by true utility iu(x,Tk)\mathrm{iu}(x,T_k)3. Once iu(x,Tk)\mathrm{iu}(x,T_k)4 patterns are in the heap, letting iu(x,Tk)\mathrm{iu}(x,T_k)5 be the smallest utility currently present, the threshold is raised dynamically by

iu(x,Tk)\mathrm{iu}(x,T_k)6

The significance of PEUCS lies in its role as the bridge between single-item prefiltering and deeper itemset search. It provides sufficient 2-item utility and periodicity information to make a substantial threshold adjustment before more expensive utility-list joins dominate execution.

5. Complexity and empirical effects

The analytical cost of building PEUCS is

iu(x,Tk)\mathrm{iu}(x,T_k)7

which is iu(x,Tk)\mathrm{iu}(x,T_k)8 when iu(x,Tk)\mathrm{iu}(x,T_k)9 and the average transaction length is xyx \prec y00 (Zhou et al., 19 Sep 2025). Its space complexity is xyx \prec y01 for storing pair entries, where xyx \prec y02 is the number of items after single-item pruning. Computing PCUD from PEUCS is xyx \prec y03 time with xyx \prec y04 extra space, while PIU is xyx \prec y05 (Zhou et al., 19 Sep 2025).

During the depth-first search, the usual utility-list joins remain dominant. The paper states that pruning by RTWU, RU, and maxPer/avgPer reduces the number of constructed lists; in the worst case the search can still be exponential in xyx \prec y06, but raised xyx \prec y07 and periodicity pruning reduce the search dramatically in practice (Zhou et al., 19 Sep 2025).

The experimental results reported for the threshold-raising strategies associated with PEUCS are specific. On six real datasets with negative profits, introducing PCUD and PRU on top of PIU reduced overall runtime by about 5% on average (Zhou et al., 19 Sep 2025). On dense datasets with many positive co-occurrences, namely mushroom_negative and kosarak_negative, runtime fell by up to 50%, and for chess_negative by about 10% (Zhou et al., 19 Sep 2025). Memory usage fell by about 2% overall, with a peak gain of 30% on mushroom_negative, which the paper attributes to fewer candidate utility lists being kept in memory (Zhou et al., 19 Sep 2025).

These results indicate that the principal value of PEUCS is not asymptotic improvement of the full search problem, but earlier and more aggressive threshold raising that lowers the practical cost of subsequent exploration.

6. Running example and interpretive significance

The paper presents a toy database of ten transactions with transaction identifiers xyx \prec y08 through xyx \prec y09 over items xyx \prec y10, with external utilities given in the paper and periodicity thresholds

xyx \prec y11

(Zhou et al., 19 Sep 2025).

In the first scan, single-item utilities are computed and PIU is applied. The retained positive-utility items are:

  • xyx \prec y12
  • xyx \prec y13
  • xyx \prec y14
  • xyx \prec y15

Items xyx \prec y16 are negative and discarded at that stage. Sorting xyx \prec y17 gives a 3rd largest value of xyx \prec y18, so the first threshold becomes

xyx \prec y19

(Zhou et al., 19 Sep 2025).

In the rescan, PEUCS is built. For transaction xyx \prec y20 with xyx \prec y21, items xyx \prec y22 produce pairs such as:

  • xyx \prec y23: xyx \prec y24, xyx \prec y25, xyx \prec y26, xyx \prec y27
  • xyx \prec y28: xyx \prec y29, xyx \prec y30

After all ten transactions, the paper reports example PEUCS entries from Table 7:

PCUD then keeps pairs with xyx \prec y34 and satisfying xyx \prec y35. Their utility values, sorted, include:

  • xyx \prec y36
  • xyx \prec y37
  • xyx \prec y38

The 3rd largest is xyx \prec y39, yielding

xyx \prec y40

(Zhou et al., 19 Sep 2025).

During the subsequent depth-first search, the first periodic high-utility itemsets found include xyx \prec y41, xyx \prec y42, and xyx \prec y43. Once these three fill the top-xyx \prec y44 heap, the smallest utility among them is xyx \prec y45, so

xyx \prec y46

and any partial candidate whose xyx \prec y47, or xyx \prec y48, or xyx \prec y49 is pruned immediately (Zhou et al., 19 Sep 2025). The final top-3 patterns are xyx \prec y50, xyx \prec y51, and xyx \prec y52.

A plausible implication is that the example is structured to show PEUCS as an intermediate representation that materially sharpens the threshold before recursive search begins in earnest. The paper’s summary makes this interpretation explicit: PEUCS provides a compact, one-pass aggregation of all 2-item co-occurrences’ positive and negative utilities together with full periodicity statistics, and this precomputed structure underlies PCUD while reducing the number of utility-list joins in the subsequent search (Zhou et al., 19 Sep 2025).

Definition Search Book Streamline Icon: https://streamlinehq.com
References (1)

Topic to Video (Beta)

No one has generated a video about this topic yet.

Whiteboard

No one has generated a whiteboard explanation for this topic yet.

Follow Topic

Get notified by email when new papers are published related to Period-estimated Utility Co-occurrence Structure (PEUCS).