Spam Detection via Browsing History Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for preventing spam account registration are inadequate due to limited information provided during the registration process, making it difficult to determine whether an email account is created for legitimate or spamming purposes.
Innovation Solution
A computer-implemented method that analyzes the browsing history data of a client device to assess the likelihood of a user being a human or a bot, using a machine learning algorithm to determine a user score and potentially a spammer score, which informs restrictive actions such as refusing account creation or implementing CAPTCHA challenges.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If keyword filtering is used to reduce spam messages, then the filtering process is simple and fast, but spam senders can easily circumvent it by replacing letters with similar but computationally distinct characters
Solution Approach 1:
The patent introduces an intermediary verification system that uses CAPTCHA challenges as a mediator between the registration process and account creation. This intermediary layer verifies user authenticity without requiring complex keyword filtering, thereby maintaining filtering speed while improving accuracy by blocking automated spam bots that would otherwise circumvent simple keyword filters
Solution Approach 2:
The patent changes the verification parameter from text-based keyword matching to behavior-based CAPTCHA verification. By shifting from analyzing message content parameters to analyzing user interaction parameters (click patterns, response time, mouse movements), the system achieves both simplicity and reliability in spam detection
2Measurement precision
If account registration requests are analyzed in detail to determine spam likelihood, then spam detection accuracy improves, but the computational burden on email servers increases
Solution Approach 1:
The patent performs preliminary spam detection analysis during the account registration phase before full account creation. By conducting CAPTCHA verification and initial spam likelihood assessment at this early stage, the system prevents resource-intensive processing of confirmed spam accounts, thereby improving detection accuracy while managing server energy consumption
Solution Approach 2:
The patent applies partial analysis by focusing only on critical verification parameters (CAPTCHA response validity, registration pattern anomalies) rather than performing exhaustive analysis of all registration data. This selective approach achieves sufficient detection accuracy without the full computational burden of complete account profile analysis
3Reliability
If CAPTCHA challenges are implemented to verify user authenticity, then automated bot registration is reduced, but the registration process becomes more complex and time-consuming
Solution Approach 1:
The patent implements partial CAPTCHA verification by applying challenges selectively based on spam likelihood assessment. Not all registration requests trigger CAPTCHA - only those exhibiting suspicious patterns (multiple rapid registrations, anomalous IP behavior, mismatched registration data). This approach maintains user authenticity verification for at-risk cases while preserving registration simplicity for legitimate users
Solution Approach 2:
The patent applies different verification qualities to different registration scenarios. High-risk registrations receive rigorous CAPTCHA verification with multiple challenges, while low-risk registrations experience streamlined or no verification. This localized quality approach ensures reliability where needed while maintaining ease of operation where risk is minimal
Data Source
AI summary
A computer implemented method for detecting an preventing spam account generation is disclosed. The method comprises receiving, by the email server, a request from the browser application to create an email account for at least one of sending and receiving an electronic message over the communication network, the request comprising at least the unique browser ID, acquiring, a browsing history data associated with the unique browser ID, the browsing history data being indicative of the browser application's browsing history with the at least one web resource; analyzing the browsing history data to determine a user score of the request, the user score being indicative of a likelihood that the user is one of a human or a bot executed by a computer application; and upon determining that the user score is indicative of a higher likelihood that the user is the bot, performing a restrictive action to the request.


