Application Identity Verification via Binary Extraction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional methods for verifying the identity of applications making service requests are burdensome, relying on circular identification processes that require shared secrets, which can be inefficient for merchant services.

Innovation Solution

A method where a merchant service system creates application program code with identifying information, which is extracted and stored by an application service system, allowing users to initiate service requests with an access token that verifies the application's identity upon comparison with stored information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional web token authentication with shared secrets is used, then application identity verification is achieved, but the process becomes burdensome and complex for merchant services

Engineering Contradiction:
Improveapplication identity verificationVSAvoidauthentication process complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the identifying information from the application binary itself, separating the verification mechanism from the shared secret authentication process. The application code contains embedded identifying information that can be directly extracted and verified by the merchant service system, eliminating the need for complex web token exchanges and shared secret management.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The identifying information is extracted and stored by the merchant service system in advance, before the actual service request occurs. This preliminary extraction and storage of identification data from the application binary simplifies the subsequent authentication process, as the system already has the verification data ready when the application makes a service request.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If shared secrets are used for authentication, then security is maintained, but the circular identification process increases operational burden

Engineering Contradiction:
ImprovesecurityVSAvoidoperational burden on merchant services
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The application effectively identifies itself through the embedded identifying information in its binary, without requiring a circular authentication process. The merchant service system extracts this information and compares it against stored data, allowing the application to self-verify its identity without involving complex shared secret exchanges between multiple parties.

Inventive Principle:
Principle #25Self-service

3Productivity

If identifying information is extracted from application code, then verification efficiency is improved, but the system must process and store application binaries

Engineering Contradiction:
Improveverification efficiencyVSAvoidprocessing requirements
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system extracts only the necessary identifying information from the application binary, rather than processing or storing the entire application code. This selective extraction of specific identification data reduces the processing burden while maintaining verification efficiency, as only the essential identifying elements are isolated and stored for future comparison.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3859570A1Confirming the identity of integrator applications
Publication Date: 2021.08.04 GOOGLE LLC
  • EP3859570A1 patent drawingFigure 1
  • EP3859570A1 patent drawingFigure 2
  • EP3859570A1 patent drawingFigure 3

AI summary

The invention relates to a computer-implemented method to verify identities of services making service requests, comprising: by an application service system: receiving, from a user device, a service request comprising first identifying information extracted by the user device from an application program code associated with a merchant service system, the application program code being resident on the user device; comparing the first identifying information received from the user device to second identifying information associated with the application program code associated with the merchant service system; and in response to the comparing: determining a match between the first identifying information and the second identifying information; and allowing the service request.