Captive Portal Packet Modification for Mobile Network Terminals
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In mobile communications, a second terminal cannot normally run applications or display a captive portal page customized by an operator due to incorrect encapsulation of response packets when an http request is sent, causing issues with displaying the intended portal page.
Innovation Solution
A first terminal receives a response packet from a DNS server, determines if it is stored, and if not, replaces the IP address of the target web page with a preset web page IP address to create a target response packet, which is then sent to the second terminal for displaying a preset web page.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the first terminal encapsulates all response packets into captive portal packets, then the captive portal page can be displayed, but applications cannot run normally because response packets for application requests are mistakenly encapsulated
Solution Approach 1:
The patent applies local quality by differentiating the treatment of response packets based on their source. Browser request response packets are encapsulated into captive portal packets, while application request response packets are forwarded directly without encapsulation. This selective approach ensures that only the necessary packets are modified, resolving the contradiction between displaying the captive portal page and maintaining application functionality.
2Ease of operation
If the first terminal does not encapsulate response packets, then applications can run normally, but the captive portal page cannot be displayed to users
Solution Approach 1:
The patent implements local quality by applying different processing rules to different types of response packets. Specifically, packets originating from browser requests are identified and encapsulated, while packets from application requests are left unmodified. This targeted approach ensures that the captive portal functionality is activated only where needed, without interfering with normal application operations.
3Reliability
If the first terminal modifies response packets to redirect to preset web page, then the preset web page can be displayed, but the original web page访问 is blocked
Solution Approach 1:
The patent applies preliminary action by first determining whether a response packet originates from a browser request or an application request before performing encapsulation. This pre-identification step ensures that only appropriate packets are redirected to the preset web page, while other packets maintain their original destination, thus preserving web page access flexibility while achieving the goal of displaying the preset web page when necessary.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
Embodiments of the present invention relate to a web page pushing method and apparatus, and a terminal, where the method includes: receiving, by a first terminal, a response packet, which is sent by a network side to the first terminal, for a request packet for visiting a target web page, where the response packet includes an Internet Protocol IP address of the target web page; determining whether the first terminal stores the response packet; if the first terminal stores the response packet, forwarding the response packet to a second terminal; if the first terminal does not store the response packet, storing the response packet in the first terminal, and replacing the IP address of the target web page in the response packet with an IP address of a preset web page to obtain a target response packet; and sending the target response packet to the second terminal, so that the second terminal displays the preset web page according to the target response packet. In this way, a problem that the second terminal cannot display a captive portal page customized by an operator is solved.