Purpose Hierarchy for Granular Data Retention and Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data privacy protocols face challenges in efficiently managing and retaining personal data across multiple applications, leading to resource consumption issues and inconsistent compliance with data protection regulations, particularly in handling purpose-based processing and retention periods.

Innovation Solution

The system implements purpose-based processing by associating custom-defined purposes with processing actions, using a purpose hierarchy to define retention periods for data categories, allowing for automatic application of dependent purposes and efficient data blocking and destruction based on retention periods, thereby enhancing data protection and compliance.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data is retained for multiple purposes with different retention periods, then compliance with data protection regulations is improved, but resource consumption increases due to storing duplicate data

Engineering Contradiction:
Improvecompliance with data protection regulationsVSAvoidresource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent applies universality by implementing a purpose hierarchy where a single data subject record serves multiple purposes simultaneously. The system allows one purpose to inherit retention requirements from parent purposes, enabling the same data to fulfill multiple compliance obligations without duplication. This multi-functionality approach ensures that data retention satisfies various regulatory requirements while avoiding redundant storage resources.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent implements nesting through the purpose hierarchy structure where child purposes are nested within parent purposes. The retention period of a child purpose can encompass or be encompassed by parent purpose retention periods, creating a nested temporal structure. This nesting allows the system to manage multiple retention requirements by organizing them in hierarchical layers, where inner (child) purposes are contained within outer (parent) purposes, efficiently utilizing storage resources while meeting all compliance deadlines.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If data retention periods are extended for dependent purposes, then data protection levels are improved, but data management complexity increases

Engineering Contradiction:
Improvedata protection levelsVSAvoiddata management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by pre-defining purpose hierarchies and retention period relationships before data processing occurs. The system establishes parent-child purpose relationships and their corresponding retention periods in advance, allowing automatic inheritance and calculation of retention requirements. This preliminary structuring eliminates the need for complex real-time calculations and manual management of multiple retention schedules, reducing operational complexity while maintaining high data protection standards.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms that automatically monitor purpose completion and trigger data blocking or destruction actions. The system continuously checks whether retention periods have expired and whether all dependent purposes have been fulfilled, providing real-time feedback on data status. This automated feedback loop ensures compliance with extended retention periods for dependent purposes without requiring manual intervention, thereby maintaining high data protection levels while managing complexity through automation.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If manual management of retention periods is performed, then flexibility in data processing is maintained, but productivity decreases due to increased manual effort

Engineering Contradiction:
Improveflexibility in data processingVSAvoidproductivity
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent applies self-service by enabling the system to automatically manage retention periods and purpose hierarchies without requiring manual intervention. The system autonomously calculates retention requirements, monitors purpose completion, and executes data blocking or destruction actions based on predefined rules. This self-service capability maintains flexibility in data processing through configurable purpose relationships while dramatically improving productivity by eliminating manual tracking and management efforts.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements dynamics by making the purpose hierarchy and retention period assignments flexible and adaptable. The system allows purposes to be dynamically created, modified, and associated with data subjects based on specific processing needs. Retention periods can be adjusted by modifying purpose relationships, and the system automatically recalculates and applies updated retention requirements. This dynamic approach maintains adaptability in data processing while improving productivity through automated enforcement of changing retention policies.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250013602A1Automatic instantiation of dependent purposes
Publication Date: 2025.01.09 SAP SE
  • US20250013602A1 patent drawing
  • US20250013602A1 patent drawing
  • US20250013602A1 patent drawing

AI summary

The present disclosure involves systems, software, and computer implemented methods for data privacy. One example method includes performing a processing action for a data subject for a purpose using a set of data categories that are associated with the purpose. The purpose has a retention period and is a parent purpose in a purpose hierarchy with at least one dependent purpose as a child purpose of the purpose. Dependent purpose retention periods and dependent purpose data categories are determined for each dependent purposes as respective subsets of the set of data categories. In response to an end of purpose for the purpose, data of the set of data categories is blocked. Data in the set of data categories that are not dependent purpose data categories is retained according to the retention period and data of each dependent purpose data category is retained according to a corresponding dependent retention period.