Click Verification Token for Human Interaction Validation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing content presentation systems often erroneously record interactions with content items due to software errors or malicious interventions, failing to accurately verify whether interactions are made by human users.

Innovation Solution

A method involving a client device's operating system generating and verifying message authentication codes to create a click verification token, ensuring that interactions with content items are validated independently and securely, using cryptographic techniques to prevent fraudulent activities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the application records interactions with content items, then the content platform can track user behavior and provide personalized services, but software errors or malicious interventions may cause erroneous recording of interactions

Engineering Contradiction:
Improveaccuracy of interaction recordingVSAvoidsoftware errors and malicious interventions
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary verification by generating a click verification token before the interaction is recorded. The token is created by obtaining attestation data from the operating system, generating a message authentication code, and validating it against the interaction data. This preliminary action prevents erroneous recording by verifying the interaction's authenticity in advance.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The click verification token acts as an intermediary between the interaction event and the recording system. The token includes a payload with interaction parameters and a message authentication code that mediates the verification process, ensuring that only genuine interactions are recorded while blocking software errors and malicious interventions.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the system verifies each interaction using cryptographic techniques, then security and accuracy are enhanced, but the complexity of the verification process increases

Engineering Contradiction:
Improvesecurity and accuracy of interaction verificationVSAvoidcomplexity of verification process
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system extracts the verification logic into a separate click verification token generation process. Instead of embedding complex verification logic throughout the interaction recording system, the verification is extracted into a distinct module that generates tokens independently. This modular approach maintains security and accuracy while managing complexity through separation of concerns.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The operating system provides self-service by directly generating the message authentication code in response to a request from the application. This self-service mechanism reduces the burden on the application layer, as the OS handles the cryptographic verification internally, thereby enhancing security while minimizing the complexity exposed to the application developer.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12028460B2Verifying user interactions on a content platform
Publication Date: 2024.07.02 GOOGLE LLC
  • US12028460B2 patent drawing
  • US12028460B2 patent drawing
  • US12028460B2 patent drawing

AI summary

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, to verify whether an interaction with a particular content displayed on a content platform is an interaction by an actual human user. A request to generate a click verification token can be received from a first application executing on a client device. The request can include data for a first set of parameters for a first interaction and a first message authentication code (MAC) set. If the first MAC set matches a second MAC set, which is generated using some of the data included in the request, the click verification token can be generated. The click verification token can be provided to the first application, which in turn can provide this token to a content verification system. The content verification can use this token to verify whether the first interaction is an actual human user interaction.