Data Upload Compliance Enforcement with Policy-Based Allow/Block

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software engineers face challenges in comprehending and complying with numerous and complex notices, consents, and controls (NCCs) for data use policies due to their large number and complexity, leading to incomplete or incorrect compliance, particularly when NCCs change or update.

Innovation Solution

Implementing a compliance function on a device that evaluates data uploads against accepted NCCs, ensuring compliance by allowing or blocking data uploads based on user-accepted policies, and persisting metadata for compliant usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software engineers manually review and comply with numerous NCCs, then compliance accuracy can be improved, but the complexity and time required increases significantly

Engineering Contradiction:
Improvecompliance accuracyVSAvoidcompliance process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an automated compliance review system that acts as an intermediary between software engineers and NCCs. This system automatically retrieves NCCs, parses their requirements, and checks code submissions against compliance criteria, eliminating the need for engineers to manually review complex legal documents while maintaining high compliance accuracy.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the manual mechanical process of reviewing NCCs with an automated computational system. The system uses natural language processing to parse NCC texts and automated code analysis to check compliance, substituting human cognitive effort with algorithmic processing that is both faster and more reliable.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If software engineers manually track and update NCCs, then compliance can be maintained, but productivity decreases due to time-consuming processes

Engineering Contradiction:
Improvecompliance maintenanceVSAvoidsoftware development productivity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements continuous automated monitoring of NCCs and code submissions. The system continuously retrieves updated NCCs, parses them in real-time, and automatically checks new code against current compliance requirements without interrupting the software development workflow, maintaining compliance while preserving productivity.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The compliance system operates autonomously without requiring engineer intervention. It automatically retrieves NCCs, parses their requirements, checks code submissions, and provides compliance feedback, enabling the system to serve itself and eliminating the time engineers would spend on compliance tasks.

Inventive Principle:
Principle #25Self-service

3Reliability

If comprehensive NCC checking is performed, then compliance coverage is improved, but the time and resources required increase

Engineering Contradiction:
Improvecompliance coverageVSAvoidcompliance checking time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary parsing and analysis of NCCs in advance, extracting compliance criteria and requirements before code submission. This preprocessing step creates a reusable compliance rule set that can be quickly applied to multiple code submissions, achieving comprehensive coverage without repeating the full analysis for each check.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent divides the compliance checking process into distinct modular components: NCC retrieval, text parsing, criterion extraction, code analysis, and compliance determination. Each component handles a specific aspect of compliance checking independently, allowing the system to process multiple NCCs efficiently and scale without linearly increasing time requirements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20250238538A1Enforcing Compliance with Data Use Policies
Publication Date: 2025.07.24 GOOGLE LLC
  • US20250238538A1 patent drawing
  • US20250238538A1 patent drawing
  • US20250238538A1 patent drawing

AI summary

This document discloses aspects of enforcing compliance of data use policies. In aspects, a network function receives, from an application, a message that includes data to upload from a device. In response, the network function executes a compliance function associated with a type of the data in the message. The compliance function can assert a data use policy based on a state (e.g., populated) of a field of the data and determine whether a user of the device has accepted the data use policy asserted for the data in the message. The compliance function can allow the upload of the data from the device based on compliance with the data use policy or blocks the upload of the data based on a lack of compliance with the data use policy. By so doing, the compliance function can ensure that data uploaded from the device complies with user-accepted data use policies.