TCP Timestamp Mobile Device Identification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions fail to uniquely identify mobile devices across all applications and web browsers without modifying applications or URLs, due to independent cookie managers inhibiting cookie-based recognition.
Innovation Solution
A method for statistical mobile device identification using timestamps from TCP segments and other identifying information, such as IP addresses and device-type unique identifiers, to create a statistical connection between native applications and an advertising server, allowing for device recognition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If cookie jars are used for device identification, then device recognition is improved within a single application, but device identification across multiple applications and web browsers deteriorates due to independent cookie managers
Solution Approach 1:
The patent introduces TCP timestamp data as an intermediary mechanism that bridges the isolation between independent cookie managers. By extracting and analyzing timestamp information from TCP segments across different applications and web browsers, the system creates a common reference point that enables cross-application device identification without requiring modifications to application-level cookie storage mechanisms.
Solution Approach 2:
The patent transitions from application-level identification (二维: application ID + cookie) to network-layer identification by utilizing TCP timestamp data. This dimensional shift allows the system to observe device behavior from a lower network layer where applications share common networking infrastructure, enabling identification across the previously isolated application boundaries.
2Ease of manufacture
If device identification is implemented without modifying applications or URLs, then ease of deployment is improved, but identification reliability deteriorates due to lack of direct device access
Solution Approach 1:
The patent leverages the device's own TCP timestamp data as a self-generated identifier. The device automatically includes timestamp information in its TCP segments without requiring any application modifications, and the server extracts this information to create device profiles. This self-service approach maintains deployment simplicity while achieving reliable identification through consistent device-generated data.
Solution Approach 2:
The system implements feedback loops where timestamp data from multiple connections is collected, analyzed, and used to refine device identification accuracy. By continuously gathering timestamp patterns from various applications and web browsers, the system builds more reliable device profiles over time, compensating for the lack of direct device access through statistical analysis.
Data Source
AI summary
Methods and apparatus for mobile device identification using TCP segment timestamps are disclosed. A request from a mobile device is received at a server. A TCP connection, initiated by the mobile device, is made between the server and the device, and a timestamp generated by the mobile device is retrieved from the options field of the TCP SYN segment. Other identifying information is received from the mobile device source, including an IP address, port, and HTTP headers. Based on the identifying information, the mobile device timestamp, and a current timestamp generated by the server, a likelihood is determined that the particular mobile device previously communicated with the server.