Proxy Server Device ID Tracking for Virtualized Apps

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for tracking device IDs for virtualized applications often attribute actions to the emulator device ID instead of the actual originating device, leading to lost revenue and inaccurate usage attribution due to the temporary validity of emulator device IDs.

Innovation Solution

A computer-implemented method involving a proxy server or network message inspector that receives, inspects, and replaces the emulator device ID with the originating device ID in network messages, ensuring accurate attribution by transmitting the corrected messages to destination servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If device ID tracking is performed using emulator device IDs, then device identification is achieved, but tracking accuracy and revenue attribution deteriorate because emulator device IDs are temporary and not linked to actual originating devices

Engineering Contradiction:
Improvedevice ID tracking accuracyVSAvoidoriginating device identification
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent introduces a device ID mapping service as an intermediary between the emulator device ID and the actual originating device ID. The mapping service stores the correspondence between emulator device IDs and real device IDs, allowing accurate attribution while maintaining the temporary nature of emulator IDs. This resolves the contradiction by preserving tracking accuracy without requiring permanent changes to the emulator ID system.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If emulator device IDs are used for tracking, then implementation simplicity is maintained, but long-term analytics and revenue attribution are compromised due to the temporary validity of emulator device IDs

Engineering Contradiction:
Improvetracking system implementationVSAvoiddevice ID validity period
Core Design Contradiction:
Ease of manufactureVSDuration of action of stationary object

Solution Approach 1:

The system performs preliminary action by pre-establishing the mapping between emulator device IDs and actual device IDs before tracking occurs. The mapping service is set up in advance to store these correspondences, enabling long-term analytics without requiring complex real-time resolution mechanisms. This maintains implementation simplicity while extending the effective duration of tracking beyond the emulator ID's temporary validity.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If direct access to raw device ID data is provided to multiple parties, then data utilization is maximized, but user privacy and data security are compromised

Engineering Contradiction:
Improvedata utilization efficiencyVSAvoiduser privacy exposure
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts only the necessary tracking information (device ID mappings and attribution data) from the raw data set, leaving sensitive personal information behind. The mapping service provides extracted, anonymized data to multiple parties for analytics and attribution purposes, maximizing data utilization while removing harmful privacy exposure. This allows productive data sharing without compromising user security.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11637907B2Systems and methods for tracking device IDs for virtualized applications
Publication Date: 2023.04.25 VERIZON PATENT & LICENSING INC
  • US11637907B2 patent drawing
  • US11637907B2 patent drawing
  • US11637907B2 patent drawing

AI summary

A method of tracking device IDs for virtualized applications includes receiving, at a proxy server, a network message originating from an emulated application, inspecting the network message to determine if a device ID is set for the network message, obtaining an originating device ID corresponding to the device ID in the network message, replacing the device ID in the network message with the originating device ID, and transmitting the network message to a specified destination server. Alternatively, the method may include intercepting the network message at a network message inspector. Alternatively, the method may include specifying the originating device ID by way of an application programming interface (API).