Declarative Entity Segmentation for Low-Overhead Tenant Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for identifying user segments in cloud platforms are resource-intensive due to the need for database normalization when dealing with multiple attribute combinations, leading to increased processing and memory overhead.

Innovation Solution

A customer data platform supports declarative expression definition for segment identification, allowing users to build complex segment expressions using a user interface that leverages the data model of each tenant, preventing invalid expressions and reducing the need for database normalization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If database normalization is performed to handle multiple attribute combinations, then data integrity is improved, but processing overhead and memory usage increase

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs data normalization and validation in advance during data ingestion, rather than during query execution. This preliminary action ensures data integrity is established upfront, eliminating the need for repeated normalization operations during segment identification queries, thus resolving the contradiction between maintaining data integrity and processing efficiency

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If complex segment expressions are allowed, then user flexibility is improved, but system complexity increases

Engineering Contradiction:
Improveuser flexibilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer consisting of pre-defined segment templates and a structured expression builder that mediates between user flexibility and system complexity. This intermediary provides a controlled interface for creating complex segments without exposing the underlying system complexity, allowing users to build flexible segment expressions through a simplified workflow

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the segment definition process into distinct, manageable components including attribute selection, operator application, and condition combination. This segmentation allows complex segment expressions to be constructed from simpler building blocks, reducing the perceived system complexity while maintaining user flexibility

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If data is stored in normalized form, then storage efficiency is improved, but query processing time increases

Engineering Contradiction:
Improvestorage efficiencyVSAvoidquery processing time
Core Design Contradiction:
Quantity of substanceVSLoss of time

Solution Approach 1:

The patent performs data normalization during the data ingestion phase rather than during query processing. This preliminary normalization action ensures that data is stored in an efficient normalized form while avoiding the time penalty of normalization during queries, as the normalization work has already been completed in advance

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20260079895A1Declarative entity segmentation
Publication Date: 2026.03.19 SALESFORCE INC
  • US20260079895A1 patent drawing
  • US20260079895A1 patent drawing
  • US20260079895A1 patent drawing

AI summary

A method for data processing includes displaying, at a user interface, a plurality of attributes that are defined by a data model configured for a tenant of a multi-tenant system. The plurality of attributes includes a one-to-many attribute that is configured to support multiple inputs and a direct attribute configured to support a single input. The method may further include receiving a selection of a first one-to-many attribute for defining an expression for identifying a segment of entities. The method may further include activating, for selection at the user interface, a subset of the attributes based on each attribute of the subset being dependent on the first attribute. The method may further include receiving an indication of the expression, executing a database query to identify the segment of entities, and transmitting, to a content communication system, an indication of the segment of entities.