Captive Portal Pop Up Suppression via HTTP Request Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Client electronic devices often face interruptions in accessing visitor-based communication services due to limited functionalities of captive browsers, which cannot properly load and execute captive portals, leading to unintended blocking of Internet connectivity, especially in environments like aircraft where such services are the only means of connectivity.
Innovation Solution
Implementing a system that monitors and handles HTTP request traffic by maintaining dynamic lists of URLs corresponding to HTTP captivity probes, allowing known probes to pass through and redirecting unknown probes to prevent captive browser activation, while using machine learning to identify new probes and update the lists accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the system redirects all HTTP requests to the captive portal, then authentication and service access control are ensured, but client devices experience interruptions and inability to access Internet connectivity
Solution Approach 1:
The patent segments HTTP requests into two categories: captivity probes and legitimate requests. The system analyzes request characteristics (URL patterns, user agents, request frequencies) to differentiate between probe requests from captive browsers and legitimate Internet requests from fully-capable browsers. This segmentation allows selective handling - redirecting only probes while allowing legitimate requests to pass through, thus resolving the contradiction between access control and connectivity continuity
Solution Approach 2:
The patent introduces an intermediary component (HTTP request handler/interceptor) positioned between the client devices and the captive portal. This intermediary monitors incoming HTTP requests, identifies captivity probes through analysis of request characteristics, and selectively redirects only those probes to the captive portal while allowing legitimate requests to proceed directly to their destinations. This intermediary mechanism maintains service control while preventing unnecessary interruptions to Internet access
2Reliability
If the captive browser is used to access the captive portal, then authentication can be performed, but the limited capabilities of the captive browser prevent proper loading and execution of the portal
Solution Approach 1:
The patent inverts the traditional captive portal access model. Instead of forcing all clients through the limited captive browser to reach the portal, the system allows fully-capable browsers to access the portal directly via legitimate HTTP requests. The inversion lies in treating the captive browser as a special case requiring redirection, while normalizing direct access for capable browsers, thereby resolving the execution capability problem while preserving authentication functionality
3Measurement precision
If HTTP captivity probes are redirected to the captive portal, then network captivity detection is enabled, but continuous probing causes repeated captive browser activations and service interruptions
Solution Approach 1:
The patent implements a feedback mechanism where the system monitors HTTP request patterns over time. When a client device is identified as a captive browser (through initial probe redirection and successful portal interaction), the system learns this device's behavior pattern and adjusts future request handling accordingly. The feedback loop prevents repeated redirection of the same device's subsequent requests, thereby eliminating continuous service interruptions while maintaining accurate captivity detection for newly connecting devices
Data Source
AI summary
Systems and methods may provide connectivity to client electronic devices in a wireless communication network aboard aircraft or in another environment. During initial client device association with the wireless network, captive browser use at the client device may be minimized by directing the device to a fully-capable browser. Upon association, subsequent captivity probes transmitted by the client device may be detected and handled so as to prevent undesired re-launching of the captive browser at the client device.