User Identity Synchronization via Host Field Subdomain Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is no straightforward method for synchronizing user identities between Over The Top (OTT) providers and network operators, as OTT providers cannot read encrypted traffic and network operators cannot use IP addresses as unique identifiers, making it difficult to share user information effectively.
Innovation Solution
Modifying the Host field of HTTP(s) by adding a user identifier as a prefix subdomain, allowing the network observer to read and associate user identification information in the Server Name Indication (SNI) field of Transport Layer Security (TLS), enabling synchronization without explicit communication between OTT providers and network observers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If network operators use IP addresses as unique identifiers, then they can identify users in the network, but they cannot synchronize user identities with OTT providers because IP addresses are not unique to individual users and can change
Solution Approach 1:
The solution segments the identity synchronization problem into two independent parts: (1) OTT providers continue to use their existing identifier systems (cookies, Advertising IDs) without change, and (2) network operators use a separate mechanism (modifying the Host field in HTTP requests) to embed and transmit user identifiers. This segmentation allows each party to maintain their own identifier system while achieving synchronization through the modified Host field transmission channel.
Solution Approach 2:
The Host field modification acts as an intermediary mechanism that bridges the gap between OTT providers and network operators. By embedding user identifier information within the Host field of HTTP requests (specifically in the SNI extension of TLS), the system creates a common communication channel that both parties can use to synchronize identities without requiring direct interaction or changing existing identifier systems.
2Object-affected harmful factors
If OTT providers cannot read encrypted traffic, then user privacy is protected, but they cannot obtain user identification information from network observers for identity synchronization
Solution Approach 1:
The solution applies preliminary action by embedding the user identifier information into the Host field of HTTP requests before the encrypted TLS connection is established. The SNI extension of TLS transmits this information in plaintext during the handshake phase, allowing network observers to capture and forward the identifier to OTT providers before encryption takes effect, thus preserving both privacy and information flow.
Solution Approach 2:
The invention moves the identifier transmission to a different dimension - using the Host field (specifically the SNI extension) of the HTTP/TLS protocol rather than attempting to transmit identifiers through the encrypted application layer payload. This dimensional shift allows identifier information to be conveyed through a channel that is accessible to network observers but still maintains the integrity of the encrypted communication channel for actual user data.
3Reliability
If strict HTTP cookie policies prevent hosts from setting cookies from other hosts, then security is maintained, but tracking companies cannot share user data through direct cookie setting
Solution Approach 1:
The modified Host field serves as an intermediary that carries user identifier information between different hosts without requiring actual cookie setting from external domains. Instead of having Company B's server set a cookie directly (which would violate same-origin policy), the system uses the Host field modification to pass the identifier through the HTTP request itself, allowing data sharing while maintaining cookie security policies.
4Loss of information
If tracking companies use redirection and parameter passing to synchronize cookies, then they can join user profiles, but the process becomes complex and requires explicit communication between providers
Solution Approach 1:
The system enables self-service by automatically embedding user identifier information in the Host field of HTTP requests without requiring manual redirection or explicit synchronization protocols between companies. The identifier is passively transmitted through the normal HTTP request flow, and both OTT providers and network operators can independently extract and use this information without coordinating with each other, thus simplifying the synchronization process while maintaining profile completeness.
Data Source
AI summary
A method for synchronizing an identity of a user between a network observer and a third party includes: reading, by the network observer, a connection request sent from the user to the third party, the connection request including a host field having a host part corresponding to the third party and a sub-host part corresponding to identification information of the user; and associating, by the network observer in a database, the identification information of the user derived from the sub-host part with the identity of the user and an identity of the third party.