[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2016062077A1 - 重定向到Web页面的方法及装置 - Google Patents

重定向到Web页面的方法及装置 Download PDF

Info

Publication number
WO2016062077A1
WO2016062077A1 PCT/CN2015/079117 CN2015079117W WO2016062077A1 WO 2016062077 A1 WO2016062077 A1 WO 2016062077A1 CN 2015079117 W CN2015079117 W CN 2015079117W WO 2016062077 A1 WO2016062077 A1 WO 2016062077A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
domain name
virtual
real
data packet
Prior art date
Application number
PCT/CN2015/079117
Other languages
English (en)
French (fr)
Inventor
周术洋
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP15852824.0A priority Critical patent/EP3211863B1/en
Priority to US15/521,390 priority patent/US10432577B2/en
Publication of WO2016062077A1 publication Critical patent/WO2016062077A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5061—Pools of addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/563—Data redirection of data network streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Definitions

  • the present invention relates to the field of communications, and in particular, to a method and apparatus for redirecting to a web page.
  • web_ui has a local domain name and LAN IP (gateway address of the terminal)
  • LAN IP gateway address of the terminal
  • the user does not open the web_ui.
  • the terminal needs to actively help the user to redirect to the gateway webpage to give relevant prompts to improve the user experience.
  • the device is not connected to the Internet, the user cannot browse the webpage through the device. You need to redirect to the web_ui to prompt the user to operate the device. After the online upgrade is complete, you need to redirect to the web_ui and prompt the user to upgrade the result.
  • Solution 1 Intercept the Domain Name System (DNS) request packet sent by the PC.
  • DNS Domain Name System
  • Solution 2 intercept the tcp packet sent by the PC.
  • the redirection condition is met, the tcp message is routed to the web server of the gateway.
  • the browser tcp handshake is completed and the http request is successfully sent, an http 302 redirect is assembled to the web_ui.
  • the domain name response packet is returned to the PC for redirection to web_ui.
  • the DNS module is required to respond to a fixed virtual IP response, so that the PC browser completes the DNS resolution and successfully sends a tcp handshake message.
  • the PC browser in order to improve the efficiency of webpage access, the PC browser saves the domain name and DNS resolution in the browser cache when accessing a domain name DNS resolution is successful.
  • the corresponding relationship of the obtained IPs is for a period of time.
  • the cache is valid, when the domain name is accessed again in the same tab page, the DNS resolution is skipped and the saved IP access is directly used.
  • the PC when the redirection condition is met, the PC responds to the DNS response of the gateway address to redirect, and the PC browser saves the DNS.
  • the browser skips the DNS resolution phase and directly uses the gateway.
  • the address access will be redirected to web_ui again until the cache expires or the user reopens a tab.
  • the second domain that is redirected when the device is not connected to the network also has this defect.
  • the embodiment of the invention provides a method and a device for redirecting to a web page, so as to at least solve the redirected domain name caused by the optimization of the PC browser in the related art, and does not clear the PC when no redirection is needed. In the case of browser caching, the issue will still be redirected for a while.
  • a method for redirecting to a web page comprising: receiving, at a first device, a DNS request of a second device, and requesting at the DNS request
  • the first device sends a response message of the DNS request to the second device, where the response message carries a local preset virtual An unused virtual IP address in the IP address group, the unused virtual IP address refers to a virtual IP that has not been used to redirect the DNS response packet;
  • the first device establishes the virtual IP address and satisfies the redirection condition Corresponding relationship of the domain name; after receiving the TCP data packet sent by the second device, the first device replaces the virtual IP address carried in the TCP data packet with the specified IP address, and according to the specified IP address Forwarding an interaction data packet between the second device and the specified IP address.
  • the virtual IP carried in the TCP packet is replaced according to the specified IP, and the interactive data packet of the data is implemented by using the specified IP, including: replacing the specified IP by using a gateway address of the first device And forwarding, according to the gateway address, an interaction data packet between the second device and the gateway.
  • the virtual IP carried in the TCP packet is replaced according to the specified IP, and the data packet is implemented by using the specified IP, and the first device obtains the TCP packet from the TCP packet.
  • a destination address of the TCP packet the first device determines whether the virtual IP address corresponding to the destination address exists in the virtual IP group, and is configured to: when the judgment result is yes, find and Redirecting the domain name corresponding to the virtual IP address; replacing the virtual IP address with the real IP address of the redirected domain name, and forwarding the second device and the real IP address according to the real IP address of the redirected domain name The interaction between the data packets.
  • the method includes: performing DNS resolution on the redirected domain name, obtaining the Redirect the real IP address corresponding to the domain name.
  • the method further includes: saving, corresponding to the redirected domain name and the redirected domain name The correspondence between real IP addresses.
  • an apparatus for redirecting to a web page comprising: a receiving module configured to receive a DNS request of a second device, and the domain name requested by the DNS request is not the first And sending, by the second device, a response message of the DNS request, where the response message contains an unused virtual IP address in the local preset virtual IP address group.
  • the unused virtual IP address refers to a virtual IP that has not been used to redirect the DNS response packet; the establishing module is configured to establish a correspondence between the virtual IP address and the domain name that satisfies the redirection condition; After receiving the TCP packet sent by the second device, replacing the virtual IP address carried in the TCP packet with the specified IP address, and forwarding the second device according to the specified IP address. Specifies an interactive packet between IP addresses.
  • the replacement module includes: a first replacement unit, configured to replace the specified IP address with a gateway address of the first device when the redirection condition is met, and forward the second device according to the gateway address and the Interaction packets between gateways.
  • the replacement module further includes: an obtaining unit, configured to acquire a destination address of the TCP data packet from the TCP data packet; and a determining unit, configured to determine that the destination address is in the Whether the virtual IP address corresponding to the destination address exists in the virtual IP group; and the second replacing unit is configured to: when the determination result is yes, search for a redirected domain name corresponding to the virtual IP address; The real IP address replaces the virtual IP address, and forwards the interaction data packet between the second device and the real IP address according to the real IP address of the redirected domain name.
  • the device further includes: a parsing module configured to perform DNS resolution on the redirected domain name to obtain a real IP address corresponding to the redirected domain name.
  • the device further includes: a saving module, configured to save a correspondence corresponding to the real domain name of the redirected domain name and the redirected domain name.
  • the first device when the first device receives the DNS request of the second device, and the domain name requested by the DNS request is not the first device gateway domain name and the redirection condition is met, the first device sends the second device to the second device.
  • a response message for sending a DNS request wherein the response message carries an unused virtual IP address in the local preset virtual IP address group, and the unused virtual IP address refers to a virtual IP that has not been used to redirect the DNS response packet.
  • the first device establishes a correspondence between the virtual IP address and the domain name that satisfies the redirection condition; after receiving the TCP data packet sent by the second device, the first device replaces the virtual IP address carried in the TCP data packet with the specified IP address, and according to The specified IP address forwards the interaction data packet between the second device and the specified IP address, and solves the redirected domain name caused by the optimization of the PC browser in the related art.
  • the redirection is not required, the PC browsing is not cleared. In the case of a cache, the problem that will still be redirected for a period of time improves the user experience.
  • FIG. 1 is a flow chart of a method of redirecting to a web page according to an embodiment of the present invention
  • FIG. 2 is a block diagram showing the structure of an apparatus for redirecting to a web page according to an embodiment of the present invention
  • FIG. 3 is a block diagram 1 of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention
  • FIG. 4 is a block diagram 2 of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention
  • FIG. 5 is a block diagram 3 of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention
  • FIG. 6 is a block diagram 4 of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention
  • FIG. 7 is a flow diagram of a scheme for a mobile terminal to redirect to a gateway web page in accordance with an alternative embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for redirecting to a web page according to an embodiment of the present invention. As shown in FIG. 1 , the method steps include:
  • Step S102 The first device receives the DNS request of the second device, and when the domain name requested by the DNS request is not the first device gateway domain name and the redirection condition is met, the first device sends a response message of the DNS request to the second device. ;
  • the response message carries a virtual IP address that is not used in the local preset virtual IP address group, and the unused virtual IP address refers to a virtual IP that has not been used to redirect the DNS response packet.
  • Step S104 The first device establishes a correspondence between the virtual IP address and the domain name that satisfies the redirection condition.
  • Step S106 After receiving the TCP packet sent by the second device, the first device replaces the virtual IP address carried in the TCP packet with the specified IP address, and forwards the interaction data between the second device and the specified IP address according to the specified IP address. package.
  • the DNS response packet that is fed back to the second device by the first device carries the virtual IP, and when the first device receives the TCP packet of the second device, replaces the virtual IP in the TCP packet to implement the second
  • the data interaction between the device and the first device solves the redirected domain name caused by the optimization of the PC browser in the related art.
  • the PC browser cache is not cleared. The problem that will still be redirected for a period of time improves the user experience.
  • the specified IP address is replaced by the gateway address of the first device, and the interaction data packet between the second device and the gateway is forwarded according to the gateway address.
  • the first device obtains the destination address of the TCP packet from the TCP packet;
  • the first device determines whether the destination IP address has a virtual IP address corresponding to the destination address in the virtual IP group.
  • the redirected domain name corresponding to the virtual IP address is searched; the virtual IP address is replaced by the real IP address of the redirected domain name, and the real IP address of the redirected domain name is forwarded between the second device and the real IP address.
  • Interactive data package When the judgment result is yes, the redirected domain name corresponding to the virtual IP address is searched; the virtual IP address is replaced by the real IP address of the redirected domain name, and the real IP address of the redirected domain name is forwarded between the second device and the real IP address.
  • the manner of obtaining the real IP address may be implemented in the following manner: performing DNS resolution on the redirected domain name, and obtaining a real IP address corresponding to the redirected domain name.
  • the corresponding relationship between the redirected domain name and the real IP address of the redirected domain name is saved.
  • FIG. 2 is a structural block diagram of a device redirected to a web page according to an embodiment of the present invention, such as As shown in Figure 2, the device comprises:
  • the receiving module 22 is configured to: when receiving the DNS request of the second device, and send the response request of the DNS request to the second device, when the domain name requested by the DNS request is not the first device gateway domain name and the redirection condition is met, where
  • the response message carries a virtual IP address that is not used in the local preset virtual IP address group, and the unused virtual IP address refers to a virtual IP that has not been used to redirect the DNS response packet.
  • the establishing module 24 is coupled to the receiving module 22, and is configured to establish a correspondence between the virtual IP address and the domain name that satisfies the redirection condition;
  • the replacement module 26 is coupled to the establishing module 24, and is configured to: after receiving the TCP packet sent by the second device, replace the virtual IP address carried in the TCP packet with the specified IP address, and forward the second device and the specified according to the specified IP address.
  • FIG. 3 is a block diagram of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention.
  • the replacement module 26 further includes: a first replacing unit 32, configured to satisfy a redirection condition, The specified IP address is replaced by the gateway address of the first device, and the interaction data packet between the second device and the gateway is forwarded according to the gateway address.
  • the replacement module 26 further includes: an obtaining unit 42 configured to acquire a TCP packet from a TCP packet. Destination address
  • the determining unit 44 is coupled to the obtaining unit 42 and configured to determine whether the destination address has a virtual IP address corresponding to the destination address in the virtual IP group.
  • the second replacing unit 46 is coupled to the determining unit 44, and is configured to: when the determination result is yes, search for a redirected domain name corresponding to the virtual IP address; replace the virtual IP address with the real IP address of the redirected domain name, and according to the redirected domain name
  • the real IP address forwards the interactive packet between the second device and the real IP address.
  • FIG. 5 is a block diagram 3 of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention.
  • the apparatus further includes: a parsing module 52 coupled to the replacement unit 26, configured to perform a redirected domain name. DNS resolution, obtaining the real IP address corresponding to the redirected domain name.
  • FIG. 6 is a block diagram of a preferred structure of an apparatus for redirecting to a web page according to an embodiment of the present invention.
  • the apparatus further includes: a saving module 62 coupled to the parsing module 52, configured to save corresponding to the redirect Correspondence between the domain name and the real IP address of the redirected domain name.
  • Step S1 When the device receives the DNS request sent by the PC, when the requested domain name is not the device gateway domain name and the redirection condition is met, the virtual IP address that is not used in the preset virtual IP group is selected, and the DNS response packet is assembled. PC.
  • Step S2 Record and save the correspondence between the redirected domain name and the responding virtual IP.
  • Step S3 When the device receives the tcp data packet sent by the PC, if the redirection condition is met, the virtual IP address in the tcp data packet is replaced by the gateway address, and the interaction data packet between the PC and the gateway is forwarded;
  • the domain name of the real access address of the tcp packet is found according to the redirected domain name and the virtual IP correspondence, and then the real name of the domain name is obtained.
  • the IP address which uses the real IP to replace the virtual target address IP in the packet, and forwards the interactive packet between the PC and the real IP address.
  • Step A When the user accesses the webpage through the domain name in the PC browser, when the device receives the DNS request, it determines whether to request the gateway domain name before entering the DNS resolution process. If yes, the process ends, and the normal DNS resolution process is entered; B;
  • Step B judging whether the redirection condition is met, and when the process is not satisfied, the process ends, and the normal DNS resolution process is entered; when satisfied, step C is performed;
  • Step C picking an unused virtual IP from the set virtual IP group, and assembling the DNS response packet to respond to the PC browser;
  • Step D recording the correspondence between the domain name of the DNS request and the virtual IP of the response
  • Step E When the device receives the tcp handshake message sent by the PC browser, it determines whether the redirection condition is met, and if yes, step F is performed, and when it is not satisfied, step H is performed;
  • Step F forwarding the tcp data packet sent by the PC browser to the gateway, and forwarding the tcp response message of the gateway to the PC browser;
  • Step G After receiving the http request sent by the PC browser, the device assembles an http 302 redirect message redirected to the gateway domain name, and the process ends.
  • Step H determining whether the target address of the tcp data packet is in the set virtual IP group, if not, taking the normal data routing process, the process ends; if yes, executing step I;
  • Step I Find the domain name corresponding to the target address of the tcp packet from the recorded redirected domain name and the virtual IP correspondence relationship;
  • Step J Find the real IP address of the domain name from the recorded domain name and the real IP record. If the domain name is not found, perform DNS resolution on the domain name to obtain the real IP address of the domain name, and save the correspondence record.
  • Step K forwarding the message of the PC browser to the real IP, and forwarding the real IP packet response to the PC browser;
  • step E If the user accesses directly using IP, or if the PC browser uses cached IP access, the flow begins directly with step E.
  • the preferred embodiment of the present invention can overcome the problems and defects in the related art that are redirected to the gateway web page due to the optimized implementation of the PC browser, and improve the user experience.
  • FIG. 7 is a flowchart of a solution for redirecting a mobile terminal to a gateway web page according to an alternative embodiment of the present invention, which includes the following steps:
  • Step S702 When the user accesses the webpage through the domain name in the PC browser, when the device receives the DNS request, it determines whether to request the gateway domain name before entering the DNS resolution process.
  • the DNS requests the gateway domain name, it does not need to process, directly enters the normal DNS resolution process, and responds to the DNS response of the gateway address; if not, it proceeds to the next step.
  • Step S704 determining whether the redirection condition is met
  • the process does not need to be processed, and the normal DNS resolution process is directly performed to resolve the real IP address corresponding to the domain name. If the redirection condition is met, the process proceeds to the next step.
  • Step S706 Pick an unused virtual IP from the set virtual IP group, and assemble a DNS response packet to respond to the PC browser.
  • Step S708 Record the correspondence between the domain name of the DNS request and the virtual IP of the response;
  • Step S710 When the device receives the tcp handshake message sent by the PC browser, it determines whether the redirection condition is met.
  • step S612 When the redirection condition is satisfied, the process goes to step S612, and if it is not satisfied, the process goes to step S616.
  • Step S712 Forward the tcp data packet sent by the PC browser to the gateway, and forward the tcp response message of the gateway to the PC browser.
  • the device tcp protocol stack forwards tcp data interaction between the PC browser and the device gateway.
  • Step S714 After receiving the http request sent by the PC browser, the device assembles an http 302 redirect message redirected to the gateway domain name, and the process ends.
  • the PC browser After the PC browser completes the tcp handshake, it sends an http request message. At this time, by responding to the http 302 message, the effect of redirecting to the gateway web page is achieved.
  • Step S716 determining whether the target address of the tcp data packet is in the set virtual IP group
  • the browser When the browser sends a tcp handshake request and does not satisfy the redirection condition, it determines whether the destination address of the data packet is in the set virtual IP group. If not, the normal data routing process is followed, and the process ends; if yes, go to Step S718;
  • Step S718 Find the domain name corresponding to the target address of the tcp packet from the recorded redirected domain name and the virtual IP correspondence relationship;
  • the domain name corresponding to the tcp target virtual address is found from the information record recorded in step S708.
  • Step S720 Obtain a real IP of the domain name
  • Step S722 Forwarding the data packet exchanged between the PC browser and the real IP.
  • the method and apparatus for redirecting to a Web page provided by the embodiment of the present invention have the following beneficial effects: the redirected domain name caused by the optimization of the PC browser in the related art is solved, when it is not required When redirecting, if the PC browser cache is not cleared, the problem will still be redirected for a period of time, which improves the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种重定向到Web页面的方法及装置，其中方法包括：在第一设备接收到第二设备的DNS请求，且在DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，第一设备向第二设备发送DNS请求的响应消息（S102），其中，响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址；第一设备建立虚拟IP地址与满足重定向条件的域名的对应关系（S104）；第一设备接收第二设备发送的TCP数据包后，使用指定IP地址替换TCP数据包中携带的虚拟IP地址，并根据指定IP地址转发第二设备与指定IP地址之间的交互数据包（S106）。该技术方案解决了相关技术中由于PC浏览器的优化而导致的重定向到Web页面的问题。

Description

重定向到Web页面的方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种重定向到Web页面的方法及装置。
背景技术
随着3G、4G和无线通信技术的快速发展，越来越多的人使用数据卡、MIFI等移动终端网上冲浪。
数据卡、MIFI等设备一般都需要一个用于设置的页面，通常是以Web页面的方式呈现给用户(下文称这个Web页面为web_ui)，web_ui有个本地域名和局域网IP(终端的网关地址)，当设备和PC连接时，用户在PC的浏览器中输入该本地域名或网关IP即可打开设备的web_ui，对设备进行相关操作和设置。
一般情况下，用户不会打开web_ui，在某些条件下，当用户用浏览器打开网页时，需要终端主动帮用户重定向到网关Web页面给出相关提示，提高用户体验。如设备未联网时，用户无法通过设备浏览网页，需要重定向到web_ui，提示用户操作设备联网；在线升级完成后，需要重定向到web_ui，提示用户升级结果等场景。
目前针对设备按需重定向到web_ui的方案主要有两种：
方案1：截取PC发过来的域名系统(Domain Name System简称为DNS)请求数据包，当满足重定向条件时，组一个域名解析结果为网关地址的DNS响应包回给PC。
方案2：截取PC发过来的tcp数据包，当满足重定向条件时，将tcp消息路由到网关的Web server，当浏览器tcp握手完成，成功发出http请求时，组装一个http 302重定向到web_ui域名的响应包回给PC，达到重定向到web_ui的目的。该方案当设备未联网时，还需要DNS模块回应一个固定的虚拟IP响应，使得PC浏览器完成DNS解析，顺利发出tcp握手消息。
这两种方案都存在由于PC浏览器的优化实现带来的用户体验缺陷：PC浏览器为了提高网页访问效率，当访问一个域名DNS解析成功时，会在浏览器缓存中保存该域名和DNS解析得到的IP的对应关系一段时间，当缓存有效时，在同一个标签页中再次访问该域名时，跳过了DNS解析，直接使用保存的IP访问。对于方案一，当满足重定向条件时，给PC回应网关地址的DNS响应来重定向，PC浏览器保存了这个DNS 解析结果，在浏览器缓存的这段有效时间内，如果设备不需要重定向了，而用户继续在浏览器同一标签页中试图访问该域名时，浏览器跳过了DNS解析阶段，直接使用网关地址访问，将再次重定向到web_ui，直到该缓存失效或用户重开一个标签页。同样，方案二在设备未联网的时候重定向的域名也存在这个缺陷。
针对相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种重定向到Web页面的方法及装置，以至少解决相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题。
为了至少实现上述目的，根据本发明的一个实施例，提供了一种重定向到Web页面的方法，包括：在第一设备接收到第二设备的DNS请求，且在所述DNS请求所请求的域名不是所述第一设备网关域名且满足重定向条件时，所述第一设备向所述第二设备发送所述DNS请求的响应消息，其中，所述响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，所述未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；所述第一设备建立所述虚拟IP地址与满足重定向条件的所述域名的对应关系；所述第一设备接收所述第二设备发送的TCP数据包后，使用指定IP地址替换所述TCP数据包中携带的虚拟IP地址，并根据所述指定IP地址转发所述第二设备与所述指定IP地址之间的交互数据包。
在满足重定向条件时，根据指定IP替换所述TCP数据包中携带的虚拟IP，进而通过所述指定IP实现数据的交互数据包包括：用所述第一设备的网关地址替换所述指定IP地址，根据所述网关地址转发所述第二设备和所述网关之间的交互数据包。
在不满足重定向条件时，根据指定IP替换所述TCP数据包中携带的虚拟IP，进而通过所述指定IP实现数据的交互数据包包括：所述第一设备从所述TCP数据包中获取所述TCP数据包的目的地址；所述第一设备判断所述目的地址在所述虚拟IP组中是否存在所述目的地址对应的虚拟IP地址；设置为在判断结果为是时，查找与所述虚拟IP地址对应的重定向域名；用所述重定向域名的真实IP地址替换所述虚拟IP地址，并根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包。
可选地，根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包之后，包括：对所述重定向域名进行DNS解析，得到与所述重定向域名对应的真实IP地址。
可选地，根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包之后还包括：保存对应于所述重定向域名与所述重定向域名真实IP地址的对应关系。
根据本发明的另一实施例，提供了一种重定向到Web页面的装置，包括：接收模块，设置为在接收到第二设备的DNS请求，且在所述DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，向所述第二设备发送所述DNS请求的响应消息，其中，所述响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，所述未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；建立模块，设置为建立所述虚拟IP地址与满足重定向条件的所述域名的对应关系；替换模块，设置为在接收所述第二设备发送的TCP数据包后，使用指定IP地址替换所述TCP数据包中携带的虚拟IP地址，并根据所述指定IP地址转发所述第二设备与所述指定IP地址之间的交互数据包。
所述替换模块包括：第一替换单元，设置为在满足重定向条件时，用所述第一设备的网关地址替换所述指定IP地址，根据所述网关地址转发所述第二设备和所述网关之间的交互数据包。
在不满足重定向条件时，所述替换模块还包括：获取单元，设置为从所述TCP数据包中获取所述TCP数据包的目的地址；判断单元，设置为判断所述目的地址在所述虚拟IP组中是否存在所述目的地址对应的虚拟IP地址；第二替换单元，设置为在判断结果为是时，查找与所述虚拟IP地址对应的重定向域名；用所述重定向域名的真实IP地址替换所述虚拟IP地址，并根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包。
所述装置还包括：解析模块，设置为对所述重定向域名进行DNS解析，得到与所述重定向域名对应的真实IP地址。
所述装置还包括：保存模块，设置为保存对应于所述重定向域名与所述重定向域名真实IP地址的对应关系。
通过本发明实施例，采用在第一设备接收到第二设备的DNS请求，且在DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，第一设备向第二设备发 送DNS请求的响应消息，其中，响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；第一设备建立虚拟IP地址与满足重定向条件的域名的对应关系；第一设备接收第二设备发送的TCP数据包后，使用指定IP地址替换TCP数据包中携带的虚拟IP地址，并根据指定IP地址转发第二设备与指定IP地址之间的交互数据包，解决了相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题，提高了用户的体验效果。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的重定向到Web页面的方法流程图；
图2是根据本发明实施例的重定向到Web页面的装置结构框图；
图3是根据本发明实施例的重定向到Web页面的装置的优选结构框图一；
图4是根据本发明实施例的重定向到Web页面的装置的优选结构框图二；
图5是根据本发明实施例的重定向到Web页面的装置的优选结构框图三；
图6是根据本发明实施例的重定向到Web页面的装置的优选结构框图四；
图7是根据本发明可选实施例移动终端重定向到网关Web页面的方案流程图。
具体实施方式
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本发明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行，并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
本实施例提供了一种重定向到Web页面的方法，图1是根据本发明实施例的重定向到Web页面的方法流程图，如图1所示，该方法步骤包括：
步骤S102：在第一设备接收到第二设备的DNS请求，且在DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，第一设备向第二设备发送DNS请求的响应消息；
其中，响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；
步骤S104：第一设备建立虚拟IP地址与满足重定向条件的域名的对应关系；
步骤S106：第一设备接收第二设备发送的TCP数据包后，使用指定IP地址替换TCP数据包中携带的虚拟IP地址，并根据指定IP地址转发第二设备与指定IP地址之间的交互数据包。
通过本实施例，第一设备反馈给第二设备的DNS响应包携带有虚拟IP，在第一设备收到第二设备的TCP数据包时，替换该TCP数据包中的虚拟IP，实现第二设备和第一设备之间的数据交互，解决了相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题，提高了用户的体验效果。
在本实施例涉及到的替换虚拟IP的方式有多种，而在本实施例的一个可选实施方式中采用了以下方式实现：
在满足重定向条件时，用第一设备的网关地址替换指定IP地址，根据网关地址转发第二设备和网关之间的交互数据包。
在不满足重定向条件时，第一设备从TCP数据包中获取TCP数据包的目的地址；
第一设备判断目的地址在虚拟IP组中是否存在目的地址对应的虚拟IP地址；
在判断结果为是时，查找与虚拟IP地址对应的重定向域名；用重定向域名的真实IP地址替换虚拟IP地址，并根据重定向域名的真实IP地址转发第二设备和真实IP地址之间的交互数据包。
在本实施的另一个可选实施方式中，获取真实IP地址的方式可以通过下一方式来实现：对重定向域名进行DNS解析，得到与重定向域名对应的真实IP地址。
为了提升用户的体验效果，在获取到该重定向域名的真实IP地址之后，保存对应于重定向域名与重定向域名真实IP地址的对应关系。
本发明实施例还提供了一种重定向到Web页面的装置，该装置可以设置为实现上述本发明方法实施例，图2是根据本发明实施例的重定向到Web页面的装置结构框图，如图2所示，该装置包括：
接收模块22，设置为在接收到第二设备的DNS请求，且在DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，向第二设备发送DNS请求的响应消息，其中，响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；
建立模块24与接收模块22耦合连接，设置为建立虚拟IP地址与满足重定向条件的域名的对应关系；
替换模块26与建立模块24耦合连接，设置为在接收第二设备发送的TCP数据包后，使用指定IP地址替换TCP数据包中携带的虚拟IP地址，并根据指定IP地址转发第二设备与指定IP地址之间的交互数据包。
图3是根据本发明实施例的重定向到Web页面的装置的优选结构框图一，如图3所示，该替换模块26还包括：第一替换单元32，设置为在满足重定向条件时，用第一设备的网关地址替换指定IP地址，根据网关地址转发第二设备和网关之间的交互数据包。
图4是根据本发明实施例的重定向到Web页面的装置的优选结构框图二，如图4所示，该替换模块26还包括：获取单元42，设置为从TCP数据包中获取TCP数据包的目的地址；
判断单元44与获取单元42耦合连接，设置为判断目的地址在虚拟IP组中是否存在目的地址对应的虚拟IP地址；
第二替换单元46与判断单元44耦合连接，设置为在判断结果为是时，查找与虚拟IP地址对应的重定向域名；用重定向域名的真实IP地址替换虚拟IP地址，并根据重定向域名的真实IP地址转发第二设备和真实IP地址之间的交互数据包。
图5是根据本发明实施例的重定向到Web页面的装置的优选结构框图三，如图5所示，该装置还包括：解析模块52与替换单元26耦合连接，设置为对重定向域名进行DNS解析，得到与重定向域名对应的真实IP地址。
图6是根据本发明实施例的重定向到Web页面的装置的优选结构框图四，如图6所示，该装置还包括：保存模块62与解析模块52耦合连接，设置为保存对应于重定向域名与重定向域名真实IP地址的对应关系。
需要说明的是，装置实施例中描述的重定向到Web页面的装置对应于上述的方法实施例，其具体的实现过程在方法实施例中已经进行过详细说明，在此不再赘述。
下面结合本发明的可选实施例及附图对本发明进行举例说明。
为了解决了相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题，提高了用户的体验效果，本发明可选实施例通过如下方式解决了上述问题。
步骤S1：设备收到PC发过来的DNS请求时，当请求的域名不是设备网关域名且满足重定向条件时，选择预设的虚拟IP组中未使用的虚拟IP，组装DNS响应数据包回应给PC。
步骤S2：记录并保存重定向的域名和响应的虚拟IP的对应关系。
步骤S3：当设备收到PC发过来的tcp数据包时，如果满足重定向条件，使用网关地址替换tcp数据包中的虚拟IP，转发PC和网关之间的交互数据包；
如果不满足重定向条件且tcp数据包的目的地址在预设的虚拟IP组中时，根据重定向域名和虚拟IP对应关系找到该tcp数据包的真实访问地址的域名，然后获取该域名的真实IP地址，使用该真实IP替换数据包中的虚拟目标地址IP，转发PC和真实IP地址之间的交互数据包。
通过上述方式克服相关技术中存在的由于PC浏览器的优化实现带来的用户体验缺陷，提高用户体验。
本发明优选实施例的移动终端重定向到网关Web页面的方法包括以下步骤：
步骤A：当用户在PC浏览器通过域名访问网页时，设备收到DNS请求时，在进入DNS解析流程之前判断是否请求网关域名，如是，流程结束，进入正常的DNS解析流程；不是时执行步骤B；
步骤B：判断是否满足重定向条件，不满足时流程结束，进入正常的DNS解析流程；满足时执行步骤C；
步骤C：从设定的虚拟IP组中挑选一个未使用的虚拟IP，组装DNS响应包回应给PC浏览器；
步骤D：记录DNS请求的域名和响应的虚拟IP的对应关系；
步骤E：设备收到PC浏览器发过来的tcp握手消息时，判断是否满足重定向条件，满足时执行步骤F，不满足时跳执行步骤H；
步骤F：将PC浏览器发过来的tcp数据包转发至网关，将网关的tcp响应消息转发至PC浏览器；
步骤G：设备收到PC浏览器发过来的http请求后，组装一个重定向到网关域名的http 302重定向消息，流程结束；
步骤H：判断tcp数据包的目标地址是否为在设定的虚拟IP组中，如不在，走正常的数据路由流程，流程结束；如在，执行步骤I；
步骤I：从记录的重定向域名和虚拟IP对应关系中找到tcp数据包目标地址对应的域名；
步骤J：从记录的域名和真实IP记录中查找该域名的真实IP，如找不到，则对该域名进行DNS解析，得到该域名的真实IP，并保存对应关系记录；
步骤K：转发PC浏览器的消息至该真实IP，并将该真实IP的数据包响应转发至PC浏览器；
如果用户直接使用IP访问，或者PC浏览器使用缓存的IP访问，则流程直接从步骤E开始。
与相关技术相比，本发明优选实施例方法能克服相关技术中存在的由于PC浏览器的优化实现带来的重定向到网关Web页面的问题和缺陷，提高了用户体验。
下面结合附图7对技术方案的实施作进一步的详细描述，图7是根据本发明可选实施例移动终端重定向到网关Web页面的方案流程图，其包括如下步骤：
步骤S702：当用户在PC浏览器通过域名访问网页时，设备收到DNS请求时，在进入DNS解析流程之前判断是否请求网关域名。
如果DNS请求的是网关域名，则不需处理，直接进入正常的DNS解析流程，响应网关地址的DNS响应；如果不是，则进入下一步流程。
步骤S704：判断是否满足重定向条件；
如果不满足重定向条件，则不需处理，直接进入正常的DNS解析流程，从网络解析域名对应的真实IP；如满足重定向条件，则进入下一步流程。
步骤S706：从设定的虚拟IP组中挑选一个未使用的虚拟IP，组装DNS响应包回应给PC浏览器；
步骤S708：记录DNS请求的域名和响应的虚拟IP的对应关系；
将重定向过的域名和响应的虚拟IP对应关系记录下来，之后步骤需要使用。
步骤S710：设备收到PC浏览器发过来的tcp握手消息时，判断是否满足重定向条件；
满足重定向条件时转到步骤S612，不满足时跳转到步骤S616。
步骤S712：将PC浏览器发过来的tcp数据包转发至网关，将网关的tcp响应消息转发至PC浏览器；
设备tcp协议栈转发PC浏览器和设备网关之间的tcp数据交互。
步骤S714：设备收到PC浏览器发过来的http请求后，组装一个重定向到网关域名的http 302重定向消息，流程结束；
当PC浏览器完成tcp握手后，会发送http请求消息，此时通过响应http 302消息，达到重定向到网关Web页面的效果；
步骤S716：判断tcp数据包的目标地址是否为在设定的虚拟IP组中；
当浏览器发送tcp握手请求，而不满足重定向条件时，判断数据包的目标地址是否在设定的虚拟IP组中，如不在，走正常的数据路由流程，流程结束；如在，转到步骤S718；
步骤S718：从记录的重定向域名和虚拟IP对应关系中找到tcp数据包目标地址对应的域名；
从步骤S708记录的信息记录中找到tcp目标虚拟地址对应的域名。
步骤S720：得到该域名的真实IP；
从步骤S720记录的域名和真实IP记录中查找该域名的真实IP，如记录中找不到，则对该域名进行DNS解析，从网络得到该域名的真实IP，并保存域名和真实IP对应关系的记录；
步骤S722：转发PC浏览器和该真实IP之间交互的数据包。
以上仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种重定向到Web页面的方法及装置，具有以下有益效果：解决了相关技术中由于PC浏览器的优化而导致的重定向过的域名，当不需要重定向时，在不清除PC浏览器缓存的情况下，在一段时间内仍会重定向的问题，提高了用户的体验效果。

Claims (10)

  1. 一种重定向到Web页面的方法，包括：
    在第一设备接收到第二设备的域名DNS请求，且在所述DNS请求所请求的域名不是所述第一设备网关域名且满足重定向条件时，所述第一设备向所述第二设备发送所述DNS请求的响应消息，其中，所述响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，所述未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；
    所述第一设备建立所述虚拟IP地址与满足重定向条件的所述域名的对应关系；
    所述第一设备接收所述第二设备发送的TCP数据包后，使用指定IP地址替换所述TCP数据包中携带的虚拟IP地址，并根据所述指定IP地址转发所述第二设备与所述指定IP地址之间的交互数据包。
  2. 根据权利要求1所述的方法，其中，在满足重定向条件时，根据指定IP替换所述TCP数据包中携带的虚拟IP，进而通过所述指定IP实现数据的交互数据包包括：
    用所述第一设备的网关地址替换所述指定IP地址，根据所述网关地址转发所述第二设备和所述网关之间的交互数据包。
  3. 根据权利要求1所述的方法，其中，在不满足重定向条件时，根据指定IP替换所述TCP数据包中携带的虚拟IP，进而通过所述指定IP实现数据的交互数据包包括：
    所述第一设备从所述TCP数据包中获取所述TCP数据包的目的地址；
    所述第一设备判断所述目的地址在所述虚拟IP组中是否存在所述目的地址对应的虚拟IP地址；
    在判断结果为是时，查找与所述虚拟IP地址对应的重定向域名；用所述重定向域名的真实IP地址替换所述虚拟IP地址，并根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包。
  4. 根据权利要求3所述的方法，其中，根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包之后，包括：
    对所述重定向域名进行DNS解析，得到与所述重定向域名对应的真实IP地址。
  5. 根据权利要求4所述的方法，其中，根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包之后还包括：
    保存对应于所述重定向域名与所述重定向域名真实IP地址的对应关系。
  6. 一种重定向到Web页面的装置，包括：
    接收模块，设置为在接收到第二设备的DNS请求，且在所述DNS请求所请求的域名不是第一设备网关域名且满足重定向条件时，向所述第二设备发送所述DNS请求的响应消息，其中，所述响应消息中携带有本地预设的虚拟IP地址组中未使用的虚拟IP地址，所述未使用的虚拟IP地址是指还未用来重定向DNS响应包的虚拟IP；
    建立模块，设置为建立所述虚拟IP地址与满足重定向条件的所述域名的对应关系；
    替换模块，设置为在接收所述第二设备发送的TCP数据包后，使用指定IP地址替换所述TCP数据包中携带的虚拟IP地址，并根据所述指定IP地址转发所述第二设备与所述指定IP地址之间的交互数据包。
  7. 根据权利要求6所述的装置，其中，所述替换模块包括：
    第一替换单元，设置为在满足重定向条件时，用所述第一设备的网关地址替换所述指定IP地址，根据所述网关地址转发所述第二设备和所述网关之间的交互数据包。
  8. 根据权利要求6所述的装置，其中，在不满足重定向条件时，所述替换模块还包括：
    获取单元，设置为从所述TCP数据包中获取所述TCP数据包的目的地址；
    判断单元，设置为判断所述目的地址在所述虚拟IP组中是否存在所述目的地址对应的虚拟IP地址；
    第二替换单元，设置为在判断结果为是时，查找与所述虚拟IP地址对应的重定向域名；用所述重定向域名的真实IP地址替换所述虚拟IP地址，并根据所述重定向域名的真实IP地址转发所述第二设备和所述真实IP地址之间的交互数据包。
  9. 根据权利要求8所述的装置，其中，所述装置还包括：
    解析模块，设置为对所述重定向域名进行DNS解析，得到与所述重定向域名对应的真实IP地址。
  10. 根据权利要求9所述的装置，其中，所述装置还包括：
    保存模块，设置为保存对应于所述重定向域名与所述重定向域名真实IP地址的对应关系。
PCT/CN2015/079117 2014-10-24 2015-05-15 重定向到Web页面的方法及装置 WO2016062077A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP15852824.0A EP3211863B1 (en) 2014-10-24 2015-05-15 Method and apparatus for redirection to web page
US15/521,390 US10432577B2 (en) 2014-10-24 2015-05-15 Method and device for redirection to web page

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410583728.1A CN105592175A (zh) 2014-10-24 2014-10-24 重定向到Web页面的方法及装置
CN201410583728.1 2014-10-24

Publications (1)

Publication Number Publication Date
WO2016062077A1 true WO2016062077A1 (zh) 2016-04-28

Family

ID=55760215

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/079117 WO2016062077A1 (zh) 2014-10-24 2015-05-15 重定向到Web页面的方法及装置

Country Status (4)

Country Link
US (1) US10432577B2 (zh)
EP (1) EP3211863B1 (zh)
CN (1) CN105592175A (zh)
WO (1) WO2016062077A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019052058A1 (zh) * 2017-09-14 2019-03-21 上海斐讯数据通信技术有限公司 一种域名重定向方法和系统
WO2019080673A1 (zh) * 2017-10-27 2019-05-02 华为技术有限公司 一种域名访问方法及设备
US11153278B2 (en) * 2018-03-28 2021-10-19 Beijing Xiaomi Mobile Software Co., Ltd. Method and device for information interaction

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106534290B (zh) * 2016-11-04 2020-04-10 浙江宇视科技有限公司 一种自适应被维护设备ip地址的维护方法及装置
CN106657082B (zh) * 2016-12-27 2019-01-08 杭州盈高科技有限公司 一种快速的http重定向方法
US20190289085A1 (en) * 2018-03-13 2019-09-19 Indigenous Software, Inc. System and method for tracking online user behavior across browsers or devices
CN108712492A (zh) * 2018-05-17 2018-10-26 中兴通讯股份有限公司 一种http重定向方法、装置、路由设备及计算机存储介质
CN115150359A (zh) * 2019-08-20 2022-10-04 华为技术有限公司 域名系统查询的方法和通信装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006675A (zh) * 2009-08-31 2011-04-06 华为技术有限公司 一种数据传输方法、传输设备及移动终端
CN102752411A (zh) * 2012-06-29 2012-10-24 华为终端有限公司 重定向方法及设备
US20130318143A1 (en) * 2012-05-25 2013-11-28 Huawei Device Co.,Ltd. Access control method and system and access terminal
CN104079534A (zh) * 2013-03-27 2014-10-01 中国移动通信集团北京有限公司 一种http缓存实现方法和系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108703A (en) * 1998-07-14 2000-08-22 Massachusetts Institute Of Technology Global hosting system
JP3952860B2 (ja) * 2002-05-30 2007-08-01 株式会社日立製作所 プロトコル変換装置
US10270755B2 (en) 2011-10-03 2019-04-23 Verisign, Inc. Authenticated name resolution
US20140089661A1 (en) 2012-09-25 2014-03-27 Securly, Inc. System and method for securing network traffic
EP2787693B1 (en) * 2013-04-05 2015-12-09 Telefonaktiebolaget L M Ericsson (publ) User plane traffic handling using network address translation and request redirection

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102006675A (zh) * 2009-08-31 2011-04-06 华为技术有限公司 一种数据传输方法、传输设备及移动终端
US20130318143A1 (en) * 2012-05-25 2013-11-28 Huawei Device Co.,Ltd. Access control method and system and access terminal
CN102752411A (zh) * 2012-06-29 2012-10-24 华为终端有限公司 重定向方法及设备
CN104079534A (zh) * 2013-03-27 2014-10-01 中国移动通信集团北京有限公司 一种http缓存实现方法和系统

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019052058A1 (zh) * 2017-09-14 2019-03-21 上海斐讯数据通信技术有限公司 一种域名重定向方法和系统
WO2019080673A1 (zh) * 2017-10-27 2019-05-02 华为技术有限公司 一种域名访问方法及设备
US11095606B2 (en) 2017-10-27 2021-08-17 Huawei Technologies Co., Ltd. Domain name access method and device
US11502990B2 (en) 2017-10-27 2022-11-15 Huawei Technologies Co., Ltd. Domain name access method and device
US11153278B2 (en) * 2018-03-28 2021-10-19 Beijing Xiaomi Mobile Software Co., Ltd. Method and device for information interaction

Also Published As

Publication number Publication date
EP3211863A4 (en) 2017-11-01
CN105592175A (zh) 2016-05-18
EP3211863B1 (en) 2019-01-09
EP3211863A1 (en) 2017-08-30
US20170317967A1 (en) 2017-11-02
US10432577B2 (en) 2019-10-01

Similar Documents

Publication Publication Date Title
WO2016062077A1 (zh) 重定向到Web页面的方法及装置
US9191458B2 (en) Request routing using a popularity identifier at a DNS nameserver
EP2540064B1 (en) Enabling ipv6 mobility with nat64
WO2016023357A1 (zh) 访问网页的方法、装置及路由器
WO2015117337A1 (zh) 网络规则条目的设置方法及装置
US8078723B2 (en) Dispatching method, dispatching apparatus and dispatching system
US11689458B2 (en) Control device, control method, and program
US20160380975A1 (en) Domain Name Service Redirection for a Content Delivery Network with Security as a Service
CN103338279A (zh) 基于域名解析的优化排序方法及系统
WO2014194580A1 (zh) 浏览器重定向方法及装置
JP6118122B2 (ja) 通信装置及びその制御方法、プログラム
US20020138660A1 (en) Method and system for the redirection of client requests
CN112968955B (zh) 一种基于eBPF技术的CDN边缘节点跨机调度方法及其系统
KR101779917B1 (ko) 미디어 리소스 피드백 방법, 장치, 프로그램 및 기록매체
TW201709692A (zh) 過濾https傳輸內容的系統、方法及裝置
CN106789725B (zh) 一种实现流量重定向的方法、装置和系统
CN101483657B (zh) 一种私网用户对同侧私网设备访问的实现方法及系统
CN109302437A (zh) 一种重定向网站的方法和装置
TWI513239B (zh) 網路設備及其進行路由轉發的方法
JP6205765B2 (ja) 映像配信装置、映像配信プログラム、映像配信方法及び映像配信システム
JP2009021921A (ja) ＩＰｖ４／ＩＰｖ６デュアルスタック対応端末のための情報提示システム
WO2017097092A1 (zh) 缓存集群服务的处理方法及系统
US10122630B1 (en) Methods for network traffic presteering and devices thereof
CN103686852B (zh) 一种对交互数据进行处理的方法、设备及无线加速系统
JP3655575B2 (ja) ゲートウェイ装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15852824

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 15521390

Country of ref document: US

REEP Request for entry into the european phase

Ref document number: 2015852824

Country of ref document: EP