WO2014048255A1 - 门户推送的方法和网络设备 - Google Patents

门户推送的方法和网络设备 Download PDF

Info

Publication number
WO2014048255A1
WO2014048255A1 PCT/CN2013/083432 CN2013083432W WO2014048255A1 WO 2014048255 A1 WO2014048255 A1 WO 2014048255A1 CN 2013083432 W CN2013083432 W CN 2013083432W WO 2014048255 A1 WO2014048255 A1 WO 2014048255A1
Authority
WO
WIPO (PCT)
Prior art keywords
website
user terminal
list
bras device
identifier
Prior art date
Application number
PCT/CN2013/083432
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 EP13841686.2A priority Critical patent/EP2894833B1/en
Publication of WO2014048255A1 publication Critical patent/WO2014048255A1/zh
Priority to US14/666,902 priority patent/US9794362B2/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/563Data redirection of data network streams
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08Access security

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and network device for portal push.
  • BACKGROUND When a user needs to access the Internet, after the user successfully initiates an authentication request through the user terminal, the user starts a browser software installed on the user terminal, such as an Internet browser (Internet Explorer), and an address bar of the browser software of the user terminal. After inputting a webpage address, the user terminal initiates a Hypertext Transfer Protocol (HTTP) request to the Broadband Remote Access Server (BRAS) device.
  • HTTP Hypertext Transfer Protocol
  • BRAS Broadband Remote Access Server
  • the portal (Portal)
  • the Uniform Resource Locator (URL) of the page is sent to the user terminal through the HTTP redirection process, so that the browser software of the user terminal displays the advertisement page or the page of a certain portal website.
  • the BRAS device opens the user terminal to access the Internet.
  • This process is Portal Push.
  • operators have two main applications for Portal Push: push advertisement page and push arrears reminder page.
  • the application on the user terminal is before the user actively browses the webpage through the browser for the first time.
  • One or more HTTP requests have been automatically initiated.
  • the BRAS device After receiving the HTTP request from the user terminal, the BRAS device performs Portal push to the user terminal. Because Portal push is generally only pushed after the BRAS device receives the first HTTP request, in this case, the Portal page pushed by the BRAS device does not appear in the browser of the user terminal, and the portal push destination is not valid. Portal push, that is, the success rate of Portal push is low.
  • a portal push method is provided, which can reduce the Portal push that is invalid in the prior art, thereby improving the success rate of Portal push.
  • the first aspect provides a method for Portal push, including:
  • the BRAS device obtains a list of website identifiers
  • the BRAS device determines whether to send a portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identification list.
  • the website identifier list includes an identifier of a target website that the user actively accesses
  • the BRAS device determines whether it is necessary to send a portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list, including:
  • the BRAS device determines that the identity of the target website accessed by the user terminal does not have a match in the website identity list, the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device passes HTTP The redirect process sends a Portal page to the user terminal.
  • the website identifier list includes an identifier of a target website that the user terminal automatically initiates accessing
  • the BRAS device determines whether it is necessary to send a portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list, including:
  • the BRAS device determines that the identity of the target website accessed by the user terminal has a match in the website identity list, the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device passes HTTP The redirect process sends a Portal page to the user terminal.
  • a third possible implementation manner where the BRAS device obtains a website identifier
  • the list includes: the BRAS device receives authentication, authorization, and authorization (Authentication, Authorization and
  • AAA remote authentication dial-in user service
  • a fourth possible implementation manner is provided, where the RADIUS packet carries the website identifier list, including: The website identifier list is carried in a Vendor-Specific attribute in the RADIUS packet.
  • a fifth possible implementation manner where the BRAS device obtains a website identifier.
  • the list includes: the BRAS device receiving a command line, the command line for creating the website identification list on the BRAS device.
  • a sixth possible Implementation manner wherein the website identifier in the website identification list includes an IP address and/or a domain name.
  • a BRAS device including:
  • a receiving list unit configured to obtain a website identification list
  • Receiving a message unit configured to receive an HTTP request message sent by the user terminal, where the HTTP request message carries an identifier of the target website accessed by the user terminal;
  • a determining unit configured to determine whether to send the portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identification list.
  • the website identifier list includes an identifier of the target website that the user actively accesses; the determining unit is specifically configured to: if the identifier of the target website accessed by the user terminal is determined There is no matching item in the website identification list, and the Portal page is skipped to be sent to the user terminal; otherwise, the Portal page is sent to the user terminal through an HTTP redirection process.
  • the website identifier list includes an identifier of a target website that the user terminal automatically initiates access to;
  • the determining unit is specifically configured to: if it is determined that the identifier of the target website accessed by the user terminal has a matching item in the website identifier list, skip sending a Portal page to the user terminal; otherwise, the HTTP redirect process is The portal page is sent to the user terminal.
  • the receiving list unit is specifically configured to: Receiving a RADIUS packet sent by the AAA server, where the RADIUS packet carries the website identifier list.
  • a ninth possible implementation manner where the RADIUS packet carries the website identifier list, including:
  • the website identifier list is carried in a Vendor-Specific attribute in the RADIUS packet.
  • the receiving list unit is specifically used to : receiving a command line, the command line for creating the website identification list on the BRAS device.
  • the website identifier in the website identifier list includes an IP address and/or a domain name.
  • FIG. 1 is a flowchart of a method for portal push according to an embodiment of the present invention
  • FIG. 2 is a flowchart of still another method for portal push according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of still another method for portal push according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of a BRAS device according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a BRAS device according to an embodiment of the present invention.
  • a BRAS device obtains a website identifier list.
  • the BRAS device may be an independent BRAS device, a router with a BRAS function, or an Access Controller (AC) device in a wireless local area network.
  • AC Access Controller
  • the type of the website identifier in the website identification list may be the IP address of the website, or the domain name of the website, or the IP address of the website and the domain name of the website.
  • the same website may have only the IP address type, or only the domain name type, or both the IP address type and the domain name type.
  • the website in the list of websites includes 3 websites, ie sina.com.cn (assuming the IP address is
  • the content of the website identification list can include the following situations:
  • a partial IP address of www.sina.com.cn such as the stomach. sina.com.cn
  • the BRAS device obtains the website identifier list, and may be in at least one of the following two manners: Mode 1: The BRAS device receives the RADIUS packet sent by the AAA server, where the RADIUS packet is received. Carrying the list of website identifiers.
  • the BRAS device receives a command line, where the command line is used to create the website identifier list on the BRAS device.
  • the RADIUS packet in the first mode refers to the RADIUS packet sent by the AAA server to the BRAS device, for example, an access-accept packet or an authorization change request packet.
  • the AAA server may distribute the website identifier list in multiple RADIUS packets to the BRAS device, for example, if the website identifier is long (the J table is long enough to be completely carried in a RADIUS packet). A part of the RADIUS Access-Accept packet is sent, and the remaining part is sent in the RADIUS COA request message. For example, the vendor-specific (Vendor-Specific) in the RADIUS packet sent by the AAA server to the BRAS device. In the attribute, the list of website identifiers is carried.
  • the attributes in the RADIUS packet are a type, length, and value (Type-Length-Value, TLV).
  • the type in the TLV is used to identify different attribute types.
  • An attribute with a Type value of 26 is called a Vendor-Specific attribute.
  • the Vendor-Specif ic attribute is also a TLV structure.
  • the Vendor-Specific attribute format recommended by the RADIUS protocol is as follows:
  • Vendor-Id (cont) Vendor type
  • Vendor-Id vendor type Vendor-type
  • Vendor length Vendor length
  • Attribute-Specific attribute are also a TLV structure, which we call the sub-property of the Vendor-Specif ic attribute.
  • the sub-attributes can define the information that needs to be carried.
  • the Vendor-Specific attribute can carry multiple sub-attributes.
  • the website identifier list may be carried in a sub-attribute of the Vendor-Specific attribute, for example, by the following a and b: a) defining two different types of sub-attributes, respectively sub-attributes 1 and sub-attribute 2, wherein the sub-attribute 1 carries a website identifier of an IP address type in the website identifier list, and the sub-attribute 2 carries a website identifier of a domain name type in the website identifier list.
  • the value of the Type in the TLV of the sub-attribute 1 is 190, and the Attribute-Specif in the TLV of the sub-attribute 1 carries the website identifier of the IP address type in the website identifier list, and can be passed through the Attribute-Specific of the sub-attribute 1.
  • a TLV is defined in the field, and each TLV stores a website identifier of an IP address type. Of course, other methods may also be used to carry the website identifier of the IP address type in the sub-attribute 1.
  • the value of the Type in the TLV of the sub-attribute 2 is 191, and the Attribute-Specif in the TLV of the sub-attribute 2 carries the website identifier of the domain name type in the website identifier list, because the website identifier of the domain name type is a string, which can be passed A specific delimiter is added after each website type identifier to distinguish each website identifier.
  • the TLV can also be defined in the Attribute-Specific field of sub-attribute 2.
  • Each TLV stores a website identifier of a domain name type.
  • the website identifier of the domain name type may also be carried in the sub-attribute 2 by other methods.
  • sub-attribute 3 Define a sub-attribute, which we call sub-attribute 3, in which sub-attribute 3 carries the website identifier of the IP address type in the website identification list and the website identifier of the domain name type. Can pass in sub-attribute 3
  • TLV is defined in the Attribute-Specific field, and each TLV stores a website identifier.
  • the website identifier of the IP address type and the website identifier of the domain name address type may also be carried in the sub-attribute 3 by other methods.
  • the second detail mode is as follows: The BRAS device receives a command line, and the command line is used to create the website identity list on the BRAS device. For example, the maintenance personnel of the BRAS device can input the website identification list by inputting an Access Control List (ACL) command on the BRAS device, or input the website identification list by other commands.
  • ACL Access Control List
  • the BRAS device receives an HTTP request packet sent by a user terminal, where the HTTP request packet carries an identifier of a target website accessed by the user terminal. For example, after the user inputs the webpage address to be accessed in the address bar of the user terminal browser software, the user terminal sends an HTTP request packet to the BRAS device, where the HTTP request packet carries the target website where the webpage is located. logo. For example, the application on the user terminal automatically initiates access to a website, and the user terminal also sends an HTTP request message to the BRAS device, where the HTTP request message carries the target website accessed by the application. Logo. After receiving the HTTP request packet sent by the user terminal, the BRAS device obtains the identifier of the target website accessed by the user terminal. The identifier of the target website accessed by the user terminal may be an IP address of the target website or a domain name of the target website. For example, the user enters a string in the address bar of the user terminal browser software.
  • the BRAS device After “http: //www.sina.com.cn" and inputting the carriage return, the BRAS device receives the HTTP request message sent by the user terminal, and obtains the target website to be accessed by the user from the HTTP request message. IP address is
  • the BRAS device determines whether to send a portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list.
  • the BRAS device determines whether to send a Portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list, instead of receiving the user terminal as received in the prior art.
  • the Portal push is performed, so that the Portal push that is invalid in the prior art can be reduced, thereby improving the success rate of the Portal push.
  • a rule for determining whether the identifier of the target website accessed by the user terminal matches a match in the website identifier list is as follows:
  • the identifier of the target website accessed by the user terminal is an IP address of the target website:
  • the IP address of the target website is "174. 35. 40. 20”
  • the identifier of the website identifier includes "174. 35. 40. 20”
  • the identifier of the target website is There are matches in the list of site IDs.
  • the website identification list includes a website identifier for the stomach. sina. com. cn, according to the domain name resolution, stomach. sina
  • the IP address of com.cn is 174. 35.
  • the identifier of the target website has a match in the list of website identification. For another example, if the IP address of the target website is "174. 35. 40. 20", the logo of the website logo list is not the stomach. sina. com.cn or 174. 35. 40. 20, Then the identifier of the target website has no matching items in the website identification list.
  • the method for portal push provided by the embodiment of the present invention is configured to configure a website identifier list on a BRAS device, and after the BRAS device receives an HTTP request message sent by the user terminal, the BRAS device according to the target accessed by the user terminal Whether the identifier of the website has a matching item in the website identifier list, and determining whether to send the portal page to the user terminal, thereby reducing the number of invalid Portal pushes and improving the success rate of Portal push.
  • an embodiment of the present invention provides a method for Portal push, including: 201.
  • the BRAS device obtains a website identifier list, where the website identifier list includes an identifier of the target website that the user actively accesses.
  • the website identification list described in 201 above may be set by an operator.
  • the website in the website list may be a website with high user access frequency or a website that the user likes.
  • the list of website identifiers described in the above 201 is referred to as "white list”.
  • the BRAS device receives an HTTP request packet sent by the user terminal, where the HTTP request packet carries an identifier of the target website accessed by the user terminal.
  • the BRAS device determines that the identifier of the target website accessed by the user terminal does not have a matching item in the website identifier list, the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device The Portal page is sent to the user terminal through an HTTP redirect process.
  • the method for the Portal push provided by the embodiment of the present invention, after setting the whitelist on the BRAS device, after the BRAS device receives the HTTP request message sent by the user terminal, if the BRAS device determines that the user terminal accesses The identity of the target website has no match in the white list, and the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device sends the Portal page to the user terminal through an HTTP redirect process. Therefore, the number of invalid Portal pushes can be reduced, and the success rate of Portal push can be improved.
  • an embodiment of the present invention provides a method for portal push, which includes:
  • the BRAS device obtains a website identifier list, where the website identifier list includes an identifier of a target website that the user terminal automatically initiates access.
  • the website identifier list includes an identifier of a target website that the user terminal automatically initiates access.
  • the user terminal automatically initiates an access, which is an HTTP request automatically initiated by the software on the user terminal after the authentication request initiated by the user terminal is successful, instead of the HTTP request initiated by the user actively accessing the website.
  • an HTTP request initiated by an instant messaging software installed on a user terminal is a case where a user terminal automatically initiates an access.
  • the website identifier list described in the foregoing 301 may be set by an operator, for example, a website automatically accessed by a background software on a common user terminal is listed in the website identifier list.
  • the list of website identifiers described in the above 301 is referred to as "blacklist”.
  • the BRAS device receives an HTTP request packet sent by the user terminal, where the HTTP request packet carries an identifier of the target website accessed by the user terminal.
  • the BRAS device determines that the identifier of the target website accessed by the user terminal has a match in the website identifier list, the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device The Portal page is sent to the user terminal through an HTTP redirect process.
  • the rule of determining whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list refer to the description of 103 in the embodiment shown in FIG. 1 , and details are not described herein again.
  • the method for the portal push provided by the embodiment of the present invention, after the blacklist is set on the BRAS device, after the BRAS device receives the HTTP request message sent by the user terminal, if the BRAS device determines that the user terminal accesses The identity of the target website has a match in the blacklist, and the BRAS device skips sending a Portal page to the user terminal; otherwise, the BRAS device sends the Portal page to the user terminal through an HTTP redirect process. Therefore, the number of invalid Portal pushes can be reduced, and the success rate of Portal push can be improved.
  • the website identifier list can distinguish different users or user groups, that is, set different website identifier lists for different users or user groups, thereby improving the targeting of Portal push. .
  • a schematic diagram of a BRAS device includes: a receiving list unit 401, configured to obtain a website identifier list.
  • the receiving message unit 402 is configured to receive an HTTP request message sent by the user terminal, where the HTTP request message carries an identifier of the target website accessed by the user terminal.
  • the determining unit 403 is configured to determine whether to send a Portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list.
  • the website identifier list includes an identifier of the target website that the user actively accesses; the determining unit 403 is specifically configured to: if it is determined that the identifier of the target website accessed by the user terminal is in the website identifier list There is no match in the middle, skip sending the Portal page to the user terminal; otherwise, send the Portal page to the user terminal through the HTTP redirect process.
  • the website identifier list includes an identifier of the target website that the user terminal automatically initiates the access;
  • the determining unit 403 is specifically configured to: if it is determined that the identifier of the target website accessed by the user terminal is on the website There is a matching item in the identifier list, and the Portal page is skipped to be sent to the user terminal; otherwise, the Portal page is sent to the user terminal through an HTTP redirection process.
  • the receiving list unit 401 is specifically configured to: receive a RADIUS packet sent by the AAA server, where the RADIUS packet carries the website identifier list.
  • the RADIUS packet carrying the website identifier list includes: carrying the website identifier list in a Vendor-Specific attribute in the RADIUS packet.
  • the receiving list unit 401 is specifically configured to receive a command line, where the command line is used to create the website identifier list on the BRAS device.
  • the website identifier in the website identification list includes an IP address and/or a domain name.
  • the BRAS device provided by the embodiment of the present invention, after configuring the website identifier list on the BRAS device, after the BRAS device receives the HTTP request message sent by the user terminal, the BRAS device according to the target website accessed by the user terminal Determining whether there is a matching item in the website identifier list, and determining whether to send a Portal page to the user terminal, thereby reducing the number of invalid Portal pushes and improving the success rate of Portal push.
  • the units in the embodiment shown in Figure 4 can be combined into one or more units.
  • the units can all be implemented by hardware.
  • One of ordinary skill in the art can understand that all or part of the various methods of the above embodiments can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium, for example, a storage medium. These may include: read only memory, random read memory, disk or optical disk, and the like.
  • a schematic diagram of a BRAS device includes: a network interface 503, a processor 501, a memory 502, and a bus 504.
  • the network interface 503, the processor 501, and the memory 502 complete communication with each other through the bus 504.
  • the network interface 503 is configured to communicate with an AAA server and a user terminal.
  • the processor 501 is configured to execute program instructions.
  • the memory 502 is configured to store the program instruction, where the program instruction is used to: obtain a website identifier list; receive an HTTP request message sent by the terminal, where the HTTP request message carries the user terminal access
  • the identifier of the target website is determined according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identifier list, and whether the portal page is sent to the user terminal.
  • the website identification list includes an identifier of the target website that the user actively accesses; if the processor 501 determines that the identifier of the target website accessed by the user terminal does not have a matching item in the website identification list, skipping Sending a Portal page to the user terminal; otherwise, sending the Portal page to the user terminal through an HTTP redirect process.
  • the website identifier list includes an identifier of the target website that the user terminal automatically initiates accessing; if the processor 501 determines that the identifier of the target website accessed by the user terminal is in the website identifier list Matching, skip sending a Portal page to the user terminal; otherwise, sending a Portal page to the user terminal through an HTTP redirect process.
  • the RADIUS packet sent by the AAA server is received by the network interface 303, where the RADIUS packet carries the website identifier list, and the website identifier list is obtained from the RADIUS packet.
  • the website identifier list is carried in a Vendor-Specific attribute in the RADIUS packet.
  • the BRAS device receives a command line, and the command line is used to create the website identification list on the BRAS device.
  • the website identifier in the website identification list includes an IP address and/or a domain name.
  • the BRAS device provided by the foregoing embodiment determines whether to send a Portal page to the user terminal according to whether the identifier of the target website accessed by the user terminal has a matching item in the website identification list, thereby reducing The number of invalid Portal pushes increases the success rate of Portal push.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Accounting & Taxation (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Game Theory and Decision Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明实施例公开了一种Portal推送的方法,包括:BRAS设备获得网站标识列表,所述BRAS设备接收用户终端发来的HTTP请求报文后,根据所述用户终端访问的目标网站的标识是否在所述网站标识列表中有匹配项,确定是否向所述用户终端发送Portal页面。本发明实施例还提供相应的BRAS设备。本发明实施例技术方案,可以减少无效Portal推送的次数,提高Portal推送的成功率。

Description

门户推送的方法和网络设备 本申请要求于 2012年 9月 29日提交中国专利局、 申请号为 201210370672. 2、发明 名称为 "门户推送的方法和网络设备"的中国专利申请的优先权, 其全部内容通过引用 结合在本申请中。 技术领域 本发明涉及通信技术领域, 具体涉及一种门户 (Portal ) 推送的方法和网络设备。 背景技术 用户需要上网时, 在用户通过用户终端发起的认证请求成功后, 用户启动安装在用 户终端上的浏览器软件, 例如因特网浏览器 (Internet Explorer), 在用户终端的浏览 器软件的地址栏输入一个网页地址后,用户终端会向宽带远程接入服务器 (Broadband Remote Access Server, BRAS)设备发起超文本传输协议 (Hypertext Transfer Protocol , HTTP) 请求, BRAS 设备收到 HTTP 请求后, 将门户 (Portal ) 页面的统一资源定位符 (Uniform Resource Locator, URL)通过 HTTP重定向流程发送给用户终端, 使得用户终 端的浏览器软件显示广告页面或者某个门户网站的页面。 之后 BRAS设备打开用户终端 访问 internet的权限, 这个过程就是 Portal推送。 当前运营商进行 Portal推送主要 有两方面的应用: 推送广告页面和推送欠费提醒页面。
现有技术中, 由于互联网业务成爆炸式增长, 往往会出现这样的情况: 用户终端发 起的认证请求成功后, 该用户终端上的应用程序在用户第一次通过浏览器主动浏览网页 前, 就已经自动发起了一次或多次 HTTP请求。 BRAS设备在收到用户终端发来的 HTTP 请求后, 即向用户终端进行 Portal推送。 因为 Portal推送一般只是在 BRAS设备收到 第一次 HTTP请求后推送, 因此在这种情况下 BRAS设备推送的 Portal页面并没有出现 在用户终端的浏览器中, 没有达到 Portal推送目的, 是无效的 Portal推送, 即 Portal 推送的成功率低。即使 BRAS设备被配置为收到前几次 HTTP请求后都进行 Portal推送, 由于前几次 HTTP请求可能都是用户终端上的应用程序在用户打开浏览器软件上网浏览 网页前自动发出的, 因此仍不能提高 Portal推送的成功率。 发明内容 提供一种 Portal推送的方法, 可以减少现有技术中无效的 Portal推送, 从而提高 Portal推送的成功率。
第一方面, 提供一种 Portal推送的方法, 包括:
BRAS设备获得网站标识列表;
所述 BRAS设备接收用户终端发来的 HTTP请求报文,所述 HTTP请求报文中携带所述用 户终端访问的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否向所述用户终端发送 Portal页面。
在所述第一方面的第一种可能的实现方式中,其中所述网站标识列表包括用户主动 访问的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否需要向所述用户终端发送 Portal页面, 包括:
如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识列表 中没有匹配项, 所述 BRAS设备跳过向所述用户终端发送 Portal页面;否则, 所述 BRAS设 备通过 HTTP重定向流程将 Portal页面发送给所述用户终端。
根据所述第一方面, 提供了第二种可能的实现方式, 所述网站标识列表包括所述用 户终端自动发起访问的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否需要向所述用户终端发送 Portal页面, 包括:
如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识列表 中有匹配项, 所述 BRAS设备跳过向所述用户终端发送 Portal页面; 否则, 所述 BRAS设备 通过 HTTP重定向流程将 Portal页面发送给所述用户终端。
根据所述第一方面, 或所述第一方面的第一种可能的实现方式, 或所述第二种可能 的实现方式, 提供了第三种可能的实现方式, 所述 BRAS设备获得网站标识列表, 包括: 所述 BRAS设备接收到认证、 授权禾口计费(Authentication, Authorization and
Accounting, AAA)服务器发来的拨号用户远程认证服务(Remote Authentication Dial In User Service, RADIUS) 报文, 所述 RADIUS报文中携带所述网站标识列表。
根据所述第三种可能的实现方式, 提供了第四种可能的实现方式, 所述 RADIUS报文 中携带所述网站标识列表, 包括: 在所述 RADIUS报文中的供应商特定 (Vendor-Specific) 属性中携带所述网站标识 列表。
根据所述第一方面, 或所述第一方面的第一种可能的实现方式, 或所述第二种可能 的实现方式, 提供了第五种可能的实现方式, 所述 BRAS设备获得网站标识列表, 包括: 所述 BRAS设备接收命令行,所述命令行用于在所述 BRAS设备上创建所述网站标识列 表。
根据所述第一方面, 或所述第一方面的第一种可能的实现方式, 或所述第二种至第 五种可能实现方式中的任一种实现方式, 提供了第六种可能的实现方式, 其中网站标识 列表中的网站标识包括 IP地址和 /或域名。
第二方面, 提供一种 BRAS设备, 包括:
接收列表单元, 用于获得网站标识列表;
接收报文单元, 用于接收用户终端发来的 HTTP请求报文, 所述 HTTP请求报文中携带 所述用户终端访问的目标网站的标识;
确定单元,用于根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否向所述用户终端发送 Portal页面。
在第二方面的第一种可能的实现方式中,其中所述网站标识列表包括用户主动访问 的目标网站的标识; 所述确定单元具体用于, 如果确定所述用户终端访问的目标网站的 标识在所述网站标识列表中没有匹配项, 跳过向所述用户终端发送 Portal页面;否则, 通过 HTTP重定向流程将 Portal页面发送给所述用户终端。
根据所述第二方面, 提供了第七种可能的实现方式, 其中所述网站标识列表包括所 述用户终端自动发起访问的目标网站的标识;
所述确定单元具体用于, 如果确定所述用户终端访问的目标网站的标识在所述网站 标识列表中有匹配项, 跳过向所述用户终端发送 Portal页面; 否则, 通过 HTTP重定向流 程将 Portal页面发送给所述用户终端。
根据所述第二方面, 或所述第二方面的第一种可能的实现方式, 或第七种可能的实 现方式, 提供了第八种可能的实现方式, 所述接收列表单元具体用于: 接收到 AAA服务 器发来的 RADIUS报文, 所述 RADIUS报文中携带所述网站标识列表。
根据所述第八种可能的实现方式, 提供第九种可能的实现方式, 所述 RADIUS报文中 携带所述网站标识列表, 包括:
在所述 RADIUS报文中的 Vendor-Specific属性中携带所述网站标识列表。 根据所述第二方面, 或所述第二方面的第一种可能的实现方式, 或所述第七种可能 的实现方式, 提供第十种可能的实现方式, 所述接收列表单元具体用于: 接收命令行, 所述命令行用于在所述 BRAS设备上创建所述网站标识列表。
根据所述第二方面, 或所述第二方面的第一种可能的实现方式, 或上述第七种至第 十种可能的实现方式中的任一种实现方式, 提供第十一种可能的实现方式, 其中所述网 站标识列表中的网站标识包括 IP地址和 /或域名。
本发明实施例提供的技术方案, 通过在 BRAS设备上配置网站标识列表, 当所述 BRAS 设备接收用户终端发来的 HTTP请求报文后,所述 BRAS设备根据所述用户终端访问的目标 网站的标识是否在所述网站标识列表中有匹配项,确定是否向所述用户终端发送 Portal 页面, 从而减少无效 Portal推送的次数, 提高 Portal推送的成功率。 附图说明 图 1是本发明实施例提供的一种 Portal推送的方法流程图;
图 2是本发明实施例提供的又一种 Portal推送的方法流程图;
图 3是本发明实施例提供的又一种 Portal推送的方法流程图;
图 4是本发明实施例提供的一种 BRAS设备的示意图;
图 5是本发明实施例提供的一种 BRAS设备的示意图。 具体实施方式 下面通过附图和实施例, 对本发明实施例的技术方案做进一步的详细描述。 如图 1所示, 本发明实施例提供一种 Portal推送的方法, 包括: 101、 BRAS设备获得网站标识列表。 所述 BRAS设备, 可以是独立的 BRAS设备, 也可以是具有 BRAS功能的路由器, 也可以 是无线局域网中的接入控制器 (Access Controller, AC) 设备。 举例来说,网站标识列表中的网站标识的类型可以是网站的 IP地址,或网站的域名, 或者网站的 IP地址以及网站的域名。 网站标识列表中, 同一个网站可以只存在 IP地址类 型, 也可以只存在域名类型, 也可以既存在 IP地址类型又存在域名类型。 假设网站列表中的网站包括 3个网站, 即 . sina. com. cn (假设 IP地址为
174. 35. 40. 20, 下同), www. baidu. com (假设 IP地址为 220. 181. 111· 147, 下同), www. google, com (假设 IP地址为 74. 125. 128. 103 , 下同),则网站标识列表的内容可以包 括以下几种情况:
情况 1 :
www. sina. com. cn www. baidu. com www. google, com 情况 2:
174. 35. 40. 20 220. 181. 111. 147 74. 125. 128. 103 情况 3: www. sina. com. cn 220. 181. 111. 147 www. google, com 情况 4: www. sina. com. cn 174. 35. 40. 20 www. baidu. com 220. 181. 111. 147 www. google, com 74. 125. 128. 103 以上所列情况仅为几种组合的举例, 不构成限定。 举例来说, 有些网站可能存在多个 IP地址, 例如胃 . sina. com. cn在不同的地区有 不同的 IP地址, 所述网站标识列表中可以包括属于胃. sina. com. cn的所有的 IP地址。 当然, 为缩短所述网站标识列表, 所述网站标识列表中也可以只包括属于
www. sina. com. cn的部分 IP地址,例如胃. sina. com. cn在所述用户终端所属区域的 IP地 址。 此外, 为了节省存储空间, 当用域名来标识一个网站时, 也可以是取其全称的一部 分, 例如用 sina. com来替代 www. sina. com. cn。 举例来说, 所述 BRAS设备获得所述网站标识列表, 至少可以通过以下两种方式中的 一种- 方式一: 所述 BRAS设备接收 AAA服务器发来的 RADIUS报文, 所述 RADIUS报文中携带 所述网站标识列表。 方式二: 所述 BRAS设备接收命令行, 所述命令行用于在所述 BRAS设备上创建所述网 站标识列表。 以下详细描述方式一: 方式一中的 RADIUS报文, 是指由 AAA服务器发给 BRAS设备的 RADIUS报文, 例如可以 是认证接受报文(Access-Accept packet) ,也可以是授权变更请求报文
(Change—of—Authorization COA request packet)。 如果所述网站标识歹 (J表比较长, 以 至于在一个 RADIUS报文中中无法完整携带, AAA服务器可以将所述网站标识列表分散在 多个 RADIUS报文中发送给 BRAS设备, 例如可以在 RADIUS Access-Accept报文中发送一部 分, 剩余的部分在 RADIUS COA请求报文中发送。 举例来说, 可以在所述由 AAA服务器发给 BRAS设备的 RADIUS报文中的供应商特定 (Vendor-Specific) 属性中, 携带所述网站标识列表。
RADIUS报文中定义了很多种属性, RADIUS报文中的属性是一种类型、 长度和值 (Type-Length-Value, TLV)结构, TLV中的类型 (Type)用于标识不同的属性类型。 其中 Type值为 26的属性称为 Vendor-Specific属性。 Vendor-Specif ic属性也是一种 TLV结构, RADIUS协议推荐的 Vendor-Specific属性格式如下:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+
Type Length Vendor-Id
+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+
Vendor-Id (cont) | Vendor type | Vendor length | +_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_+
I Attribute-Specific. . .
+_+_+_+_+_+_+_+_+_+_+_+_+_+_+_ 其中- 类型 ( Type ) 的值为 26; 长度 (Length) 的值为该属性的长度; 供应商标识 (Vendor-Id) 的值为供应商标识;
Vendor-Id后面的供应商类型 (Vendor-type ) , 供应商长度 (Vendor length) 禾口 特定属性(Attribute-Specific )又是一个 TLV结构, 我们称之 Vendor-Specif ic属性的 子属性, 在该子属性中可以定义需要携带的信息。 Vendor-Specific属性中可以携带多 个子属性。 举例来说, 可以在所述 Vendor-Specific属性的子属性中携带所述网站标识列表, 例如通过下述 a和 b的方式来携带: a)定义两种不同类型的子属性, 分别为子属性 1和子属性 2, 其中子属性 1携带所述 网站标识列表中 IP地址类型的网站标识, 子属性 2携带所述网站标识列表中域名类型的 网站标识。 例如, 子属性 1的 TLV中的 Type的值为 190, 子属性 1的 TLV中 Attribute-Specif ic中携带所 述网站标识列表中 IP地址类型的网站标识, 可以通过在子属性 1的 Attribute-Specific 字段中定义 TLV, 每个 TLV存储一个 IP地址类型的网站标识。 当然, 也可以用其它方法在 子属性 1中携带 IP地址类型的网站标识。 子属性 2的 TLV中的 Type的值为 191, 子属性 2的 TLV中 Attribute-Specif ic中携带所 述网站标识列表中域名类型的的网站标识, 因为域名类型的网站标识是字符串, 可以 通过在每个域名类型的网站标识后增加特定的分隔符以区分每个网站标识, 也可以通过 在子属性 2的 Attribute-Specific字段中定义 TLV, 每个 TLV存储一个域名类型的网站标 识。 当然, 也可以用其它方法在子属性 2中携带域名类型的网站标识。 b)定义一种子属性, 我们称为子属性 3, 在子属性 3中携带所述网站标识列表中 IP地 址类型的网站标识和域名类型的的网站标识。 可以通过在子属性 3的
Attribute-Specific字段中定义 TLV, 每个 TLV存储一个网站标识。 当然, 也可以用其它 方法在子属性 3中携带 IP地址类型的网站标识和域名地址类型的网站标识。 以下详细描述方式二: 所述 BRAS设备接收命令行,所述命令行用于在所述 BRAS设备上创建所述网站标识列 表。 举例来说, BRAS设备的维护人员可以通过在 BRAS设备上输入控制访问列表(Access Control List, ACL) 命令来输入所述网站标识列表, 或者通过其他命令来输入所述网 站标识列表。
102、 所述 BRAS设备接收用户终端发来的 HTTP请求报文, 所述 HTTP请求报文中携带 所述用户终端访问的目标网站的标识。 举例来说, 当用户在用户终端浏览器软件的地址栏输入要访问的网页地址后, 用户 终端向 BRAS设备发送 HTTP请求报文,所述 HTTP请求报文中携带该网页所位于的目标网站 的标识。 又举例来说, 该用户终端上的应用程序自动发起访问某个网站, 用户终端也会向 BRAS设备发送 HTTP请求报文,所述 HTTP请求报文中携带所述应用程序所访问的目标网站 的标识。 所述 BRAS设备接收用户终端发来的 HTTP请求报文后, 获得所述用户终端访问的目标 网站的标识。 所述用户终端访问的目标网站的标识, 可以是目标网站的 IP地址, 也可以是目标网 站的域名。 例如, 用户在用户终端浏览器软件的地址栏中输入字符串
"http : //www. sina. com. cn"并输入回车后, 所述 BRAS设备接收用户终端发来的 HTTP请 求报文, 从所述 HTTP请求报文中获得用户要访问的目标网站的 IP地址为
" 174. 35. 40. 20 " (例如 www. sina. com. cn的 IP地址是 174. 35. 40. 20 ) 。 103、 所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识 列表中有匹配项, 确定是否向所述用户终端发送 Portal页面。 所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否向所述用户终端发送 Portal页面, 而不是像现有技术中收到用户 终端发来的 HTTP请求后, 即进行 Portal推送, 从而可以减少现有技术中无效的 Portal推 送, 从而提高 Portal推送的成功率。 关于判断所述用户终端访问的目标网站的标识匹配是否在所述网站标识列表中有 匹配项的规则, 说明如下: 以所述用户终端访问的目标网站的标识是目标网站的 IP地址举例: 如果所述目标网站的 IP地址为 " 174. 35. 40. 20 ", 所述网站标识列表中包括一个网 站的标识为 " 174. 35. 40. 20 ",则所述目标网站的标识在所述网站标识列表中有匹配项。 又举例来说, 如果所述目标网站的 IP地址 " 174. 35. 40. 20 " , 所述网站标识列表 中包括一个网站的标识为胃. sina. com. cn, 根据域名解析, 胃. sina. com. cn的 IP地址 是 174. 35. 40. 20, 则所述目标网站的标识在所述网站标识列表中有匹配项。 又举例来说, 如果所述目标网站的 IP地址 " 174. 35. 40. 20 " , 所述网站标识列表 中没有网站的标识为胃. sina. com. cn或 174. 35. 40. 20, 则所述目标网站的标识在所述 网站标识列表中没有匹配项。 本发明实施例提供的 Portal推送的方法, 通过在 BRAS设备上配置网站标识列表, 当 所述 BRAS设备接收用户终端发来的 HTTP请求报文后,所述 BRAS设备根据所述用户终端访 问的目标网站的标识是否在所述网站标识列表中有匹配项,确定是否向所述用户终端发 送 Portal页面, 从而减少无效 Portal推送的次数, 提高 Portal推送的成功率。
如图 2所示, 本发明实施例提供一种 Portal推送的方法, 包括: 201、 BRAS设备获得网站标识列表, 所述网站标识列表包括用户主动访问的目标网 站的标识。 关于 BRAS设备如何获得网站标识列表, 以及网站标识列表中网站标识的类型, 请参 见如图 1所示的实施例中 101的描述, 在此不再赘述。 举例来说, 上述 201中所述的网站标识列表可以由运营商来设置, 例如网站列表中 的网站可以是用户访问频率高的网站,或用户喜爱的网站。为方便后续描述,称上述 201 中所述的网站标识列表为 "白名单" 。
202、 所述 BRAS设备接收用户终端发来的 HTTP请求报文, 所述 HTTP请求报文中携带 所述用户终端访问的目标网站的标识。 203、 如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识 列表中没有匹配项,所述 BRAS设备跳过向所述用户终端发送 Portal页面;否则,所述 BRAS 设备通过 HTTP重定向流程将 Portal页面发送给所述用户终端。 关于判断所述用户终端访问的目标网站的标识是否在所述网站标识列表中有匹配 项的规则, 请参见如图 1所示的实施例中 103的描述, 在此不再赘述。 本发明实施例提供的 Portal推送的方法, 通过在 BRAS设备上设置所述白名单, 当所 述 BRAS设备接收用户终端发来的 HTTP请求报文后, 如果所述 BRAS设备确定所述用户终端 访问的目标网站的标识在所述白名单中没有匹配项,所述 BRAS设备跳过向所述用户终端 发送 Portal页面;否则, 所述 BRAS设备通过 HTTP重定向流程将 Portal页面发送给所述用 户终端, 从而可以减少无效 Portal推送的次数, 提高 Portal推送的成功率。
如图 3所示, 本发明实施例提供一种 Portal推送的方法, 包括:
301、 BRAS设备获得网站标识列表, 所述网站标识列表包括用户终端自动发起访问 的目标网站的标识。 关于 BRAS设备如何获得网站标识列表, 以及网站标识列表中网站标识的类型, 请参 见如图 1所示的实施例中 101的描述, 在此不再赘述。 所述用户终端自动发起访问, 是指在用户终端发起的认证请求成功后, 用户终端上 的软件自动发起的 HTTP请求, 而非用户主动访问网站所引发的 HTTP请求。 例如安装在用 户终端上的即时通信软件发起的 HTTP请求, 就是一种用户终端自动发起访问的情况。 举 例来说, 上述 301中所述的网站标识列表可以由运营商来设置, 例如将常见的用户终端 上的后台软件所自动访问的网站列入所述网站标识列表。 为方便后续描述, 称上述 301 中所述的网站标识列表为 "黑名单" 。
302、 所述 BRAS设备接收用户终端发来的 HTTP请求报文, 所述 HTTP请求报文中携带 所述用户终端访问的目标网站的标识。
303、 如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识 列表中有匹配项, 所述 BRAS设备跳过向所述用户终端发送 Portal页面;否则, 所述 BRAS 设备通过 HTTP重定向流程将 Portal页面发送给所述用户终端。 关于判断所述用户终端访问的目标网站的标识是否在所述网站标识列表中有匹配 项的规则, 请参见如图 1所示的实施例中 103的描述, 在此不再赘述。 本发明实施例提供的 Portal推送的方法, 通过在 BRAS设备上设置所述黑名单, 当所 述 BRAS设备接收用户终端发来的 HTTP请求报文后, 如果所述 BRAS设备确定所述用户终端 访问的目标网站的标识在所述黑名单中有匹配项,所述 BRAS设备跳过向所述用户终端发 送 Portal页面;否则, 所述 BRAS设备通过 HTTP重定向流程将 Portal页面发送给所述用户 终端, 从而可以减少无效 Portal推送的次数, 提高 Portal推送的成功率。
举例来说, 在上述图 1至图 3的实施例中, 所述网站标识列表可区分不同用户或用户 组,即针对不同用户或用户组设置不同的网站标识列表,从而提高 Portal推送的针对性。
请参考图 4, 本发明实施例提供的一种 BRAS设备的示意图, 包括: 接收列表单元 401, 用于获得网站标识列表。 接收报文单元 402, 用于接收用户终端发来的 HTTP请求报文, 所述 HTTP请求报文中 携带所述用户终端访问的目标网站的标识。 确定单元 403, 用于根据所述用户终端访问的目标网站的标识是否在所述网站标识 列表中有匹配项, 确定是否向所述用户终端发送 Portal页面。 举例来说, 其中所述网站标识列表包括用户主动访问的目标网站的标识; 所述确定 单元 403具体用于, 如果确定所述用户终端访问的目标网站的标识在所述网站标识列表 中没有匹配项, 跳过向所述用户终端发送 Portal页面;否则, 通过 HTTP重定向流程将 Portal页面发送给所述用户终端。 又举例来说,其中所述网站标识列表包括所述用户终端自动发起访问的目标网站的 标识; 所述确定单元 403具体用于, 如果确定所述用户终端访问的目标网站的标识在所 述网站标识列表中有匹配项, 跳过向所述用户终端发送 Portal页面; 否则, 通过 HTTP重 定向流程将 Portal页面发送给所述用户终端。 举例来说, 所述接收列表单元 401具体用于, 接收到 AAA服务器发来的 RADIUS报文, 所述 RADIUS报文中携带所述网站标识列表。 举例来说, 所述 RADIUS报文中携带所述网站标识列表, 包括: 在所述 RADIUS报文中 的 Vendor-Specific属性中携带所述网站标识列表。 又举例来说, 所述接收列表单元 401具体用于, 接收命令行, 所述命令行用于在所 述 BRAS设备上创建所述网站标识列表。 举例来说, 所述网站标识列表中的网站标识包括 IP地址和 /或域名。 本发明实施例提供的 BRAS设备, 通过在 BRAS设备上配置网站标识列表, 当所述 BRAS 设备接收用户终端发来的 HTTP请求报文后,所述 BRAS设备根据所述用户终端访问的目标 网站的标识是否在所述网站标识列表中有匹配项,确定是否向所述用户终端发送 Portal 页面, 从而减少无效 Portal推送的次数, 提高 Portal推送的成功率。
举例来说, 图 4中所示实施例中的单元可以合并为一个或者多个单元。 又举例来说, 所述单元均可通过硬件来实现。 本领域普通技术人员可以理解上述实 施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成, 该程序 可以存储于计算机可读存储介质中, 举例来说, 存储介质可以包括: 只读存储器、 随机 读取存储器、 磁盘或光盘等。
请参考图 5, 本发明实施例提供的一种 BRAS设备的示意图, 所述 BRAS设备包括: 网络接口 503, 处理器 501, 存储器 502, 总线 504。 所述网络接口 503, 处理器 501, 存储器 502通过所述总线 504完成相互间的通信。 所述网络接口 503, 用于与 AAA服务器和用户终端通信。 所述处理器 501, 用于执行程序指令。 所述存储器 502, 用于存放所述程序指令, 所述程序指令用于: 获得网站标识列表; 接收所述终端发来的 HTTP请求报文,所述 HTTP请求报文中携带所述用户终端访问的 目标网站的标识; 根据所述用户终端访问的目标网站的标识是否在所述网站标识列表中有匹配项,确 定是否向所述用户终端发送 Portal页面。 举例来说, 其中所述网站标识列表包括用户主动访问的目标网站的标识; 如果所述 处理器 501确定所述用户终端访问的目标网站的标识在所述网站标识列表中没有匹配 项, 跳过向所述用户终端发送 Portal页面;否则, 通过 HTTP重定向流程将 Portal页面发 送给所述用户终端。 又举例来说,其中所述网站标识列表包括所述用户终端自动发起访问的目标网站的 标识; 如果所述处理器 501确定所述用户终端访问的目标网站的标识在所述网站标识列 表中有匹配项, 跳过向所述用户终端发送 Portal页面; 否则, 通过 HTTP重定向流程将 Portal页面发送给所述用户终端。 举例来说, 通过所述网络接口 303接收 AAA服务器发来的 RADIUS报文, 所述 RADIUS报 文中携带所述网站标识列表, 从所述 RADIUS报文获得所述网站标识列表。 举例来说,在所述 RADIUS报文中的 Vendor-Specific属性中携带所述网站标识列表。 举例来说, 所述 BRAS设备接收命令行, 所述命令行用于在所述 BRAS设备上创建所述 网站标识列表。 举例来说, 所述网站标识列表中的网站标识包括 IP地址和 /或域名。 上述实施例提供的 BRAS设备, 通过获得网站标识列表, 根据所述用户终端访问的目 标网站的标识是否在所述网站标识列表中有匹配项, 确定是否向所述用户终端发送 Portal页面, 从而减少无效 Portal推送的次数, 提高 Portal推送的成功率。
以上对本发明实施例所提供的 Portal推送的方法和网络设备进行了详细介绍,但以 上实施例的说明只是用于帮助理解本发明的方法及其核心思想, 不应理解为对本发明的 限制。 本技术领域的技术人员在本发明揭露的技术范围内, 可轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。

Claims

权利要求
1、 一种门户 Portal推送的方法, 其特征在于, 包括:
宽带远程接入服务器 BRAS设备获得网站标识列表;
所述 BRAS设备接收用户终端发来的超文本传输协议 HTTP请求报文,所述 HTTP请求报 文中携带所述用户终端访问的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否向所述用户终端发送 Portal页面。
2、 根据权利要求 1所述的方法, 其特征在于, 所述网站标识列表包括用户主动访问 的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否需要向所述用户终端发送 Portal页面, 包括:
如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识列表 中没有匹配项, 所述 BRAS设备跳过向所述用户终端发送 Portal页面;否则, 所述 BRAS设 备通过 HTTP重定向流程将 Portal页面发送给所述用户终端。
3、 根据权利要求 1所述的方法, 其特征在于, 所述网站标识列表包括所述用户终端 自动发起访问的目标网站的标识;
所述 BRAS设备根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否需要向所述用户终端发送 Portal页面, 包括:
如果所述 BRAS设备确定所述用户终端访问的目标网站的标识在所述网站标识列表 中有匹配项, 所述 BRAS设备跳过向所述用户终端发送 Portal页面; 否则, 所述 BRAS设备 通过 HTTP重定向流程将 Portal页面发送给所述用户终端。
4、 根据权利要求 1至 3任一所述的方法, 其特征在于, 所述 BRAS设备获得网站标识 列表, 包括:
所述 BRAS设备接收到认证、 授权和计费 AAA服务器发来的拨号用户远程认证服务 RADIUS报文, 所述 RADIUS报文中携带所述网站标识列表。
5、 根据权利要求 4所述的方法, 其特征在于, 所述 RADIUS报文中携带所述网站标识 列表, 包括:
在所述 RADIUS报文中的供应商特定 Vendor-Specific属性中携带所述网站标识列 表。
6、 根据权利要求 1至 3任一所述的方法, 其特征在于, 所述 BRAS设备获得网站标识 列表, 包括:
所述 BRAS设备接收命令行,所述命令行用于在所述 BRAS设备上创建所述网站标识列 表。
7、 根据权利要求 1至 6任一所述的方法, 其特征在于, 所述网站标识列表中的网站 标识包括 IP地址和 /或域名。
8、 一种宽带远程接入服务器 BRAS设备, 其特征在于, 包括:
接收列表单元, 用于获得网站标识列表;
接收报文单元, 用于接收用户终端发来的超文本传输协议 HTTP请求报文, 所述 HTTP 请求报文中携带所述用户终端访问的目标网站的标识;
确定单元,用于根据所述用户终端访问的目标网站的标识是否在所述网站标识列表 中有匹配项, 确定是否向所述用户终端发送 Portal页面。
9、 根据权利要求 8所述的 BRAS设备, 其特征在于, 所述网站标识列表包括用户主动 访问的目标网站的标识;
所述确定单元具体用于, 如果确定所述用户终端访问的目标网站的标识在所述网站 标识列表中没有匹配项, 跳过向所述用户终端发送 Portal页面;否则, 通过 HTTP重定向 流程将 Portal页面发送给所述用户终端。
10、 根据权利要求 8所述的 BRAS设备, 其特征在于, 所述网站标识列表包括所述用 户终端自动发起访问的目标网站的标识;
所述确定单元具体用于, 如果确定所述用户终端访问的目标网站的标识在所述网站 标识列表中有匹配项, 跳过向所述用户终端发送 Portal页面; 否则, 通过 HTTP重定向流 程将 Portal页面发送给所述用户终端。
11、 根据权利要求 8至 10任一所述的 BRAS设备, 其特征在于, 所述接收列表单元具 体用于: 接收到认证、 授权和计费 AAA服务器发来的拨号用户远程认证服务 RADIUS报文, 所述 RADIUS报文中携带所述网站标识列表。
12、 根据权利要求 11所述的 BRAS设备, 其特征在于, 所述 RADIUS报文中携带所述网 站标识列表, 包括:
在所述 RADIUS报文中的供应商特定 Vendor-Specific属性中携带所述网站标识列 表。
13、 根据权利要求 8至 10任一所述的 BRAS设备, 其特征在于, 所述接收列表单元具 体用于: 接收命令行, 所述命令行用于在所述 BRAS设备上创建所述网站标识列表。
14、 根据权利要求 8至 13任一所述的 BRAS设备, 其特征在于, 所述网站标识列表中 的网站标识包括 IP地址和 /或域名。
PCT/CN2013/083432 2012-09-29 2013-09-13 门户推送的方法和网络设备 WO2014048255A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13841686.2A EP2894833B1 (en) 2012-09-29 2013-09-13 Portal push method and network equipment
US14/666,902 US9794362B2 (en) 2012-09-29 2015-03-24 Portal push method and network equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210370672.2A CN102868758B (zh) 2012-09-29 2012-09-29 门户推送的方法和网络设备
CN201210370672.2 2012-09-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/666,902 Continuation US9794362B2 (en) 2012-09-29 2015-03-24 Portal push method and network equipment

Publications (1)

Publication Number Publication Date
WO2014048255A1 true WO2014048255A1 (zh) 2014-04-03

Family

ID=47447344

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/083432 WO2014048255A1 (zh) 2012-09-29 2013-09-13 门户推送的方法和网络设备

Country Status (4)

Country Link
US (1) US9794362B2 (zh)
EP (1) EP2894833B1 (zh)
CN (1) CN102868758B (zh)
WO (1) WO2014048255A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3128713A1 (en) * 2014-04-04 2017-02-08 ZTE Corporation Page push method, device and server, and centralized network management controller

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868758B (zh) 2012-09-29 2016-12-21 华为技术有限公司 门户推送的方法和网络设备
CN104219263B (zh) * 2013-05-31 2017-11-10 中国电信股份有限公司 欠费提醒信息的推送处理方法与系统
CN104426660A (zh) * 2013-09-04 2015-03-18 中兴通讯股份有限公司 一种Portal认证方法、BNG、Portal服务器和系统
CN105991589B (zh) * 2015-02-13 2019-04-26 华为技术有限公司 一种用于重定向的方法、装置及系统
US10180985B2 (en) * 2015-02-19 2019-01-15 At&T Intellectual Property I, L.P. Apparatus and method for automatically redirecting a search
EP3340072B1 (de) * 2016-12-23 2021-02-17 Solute GmbH Verfahren zur durchführung einer selbsttätigen datenabfrage und programmprodukt
US10547614B2 (en) * 2017-03-30 2020-01-28 Juniper Networks, Inc. Bulk delivery of change of authorization data via AAA protocols
CN111385173B (zh) * 2018-12-28 2023-08-25 中兴通讯股份有限公司 一种报文处理方法、装置、控制面设备和计算机存储介质
CN109951487A (zh) * 2019-03-22 2019-06-28 杭州迪普科技股份有限公司 一种Portal认证方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217560A (zh) * 2007-12-29 2008-07-09 杭州华三通信技术有限公司 一种页面的推送方法、系统和装置
CN101217568A (zh) * 2008-01-15 2008-07-09 杭州华三通信技术有限公司 一种页面的推送方法、系统和装置
CN102075583A (zh) * 2011-01-30 2011-05-25 杭州华三通信技术有限公司 一种http请求报文处理方法及其设备
US20120166662A1 (en) * 2010-12-22 2012-06-28 Pradeep Iyer HTTP Proxy based Captive Portal
CN102868758A (zh) * 2012-09-29 2013-01-09 华为技术有限公司 门户推送的方法和网络设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6636894B1 (en) * 1998-12-08 2003-10-21 Nomadix, Inc. Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability
ES2243319T3 (es) * 1999-10-22 2005-12-01 Nomadix, Inc. Sistema y procedimiento para redireccionar a usuarios que intentan acceder a un destino de red.
EP1381199B1 (en) * 2002-07-12 2006-09-27 Alcatel Firewall for dynamically granting and denying network resources
US20060069782A1 (en) * 2004-09-16 2006-03-30 Michael Manning Method and apparatus for location-based white lists in a telecommunications network
US8205246B2 (en) * 2007-05-10 2012-06-19 Cisco Technology, Inc. User sensitive filtering of network application layer resources
CN101741888A (zh) 2008-11-11 2010-06-16 中国移动通信集团上海有限公司 推送认证页面的方法、系统及装置
US8788653B2 (en) * 2011-01-05 2014-07-22 F-Secure Corporation Controlling access to web content
US8650495B2 (en) * 2011-03-21 2014-02-11 Guest Tek Interactive Entertainment Ltd. Captive portal that modifies content retrieved from designated web page to specify base domain for relative link and sends to client in response to request from client for unauthorized web page
CN102891826B (zh) * 2011-06-27 2015-09-30 华为技术有限公司 网页访问的控制方法、设备和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101217560A (zh) * 2007-12-29 2008-07-09 杭州华三通信技术有限公司 一种页面的推送方法、系统和装置
CN101217568A (zh) * 2008-01-15 2008-07-09 杭州华三通信技术有限公司 一种页面的推送方法、系统和装置
US20120166662A1 (en) * 2010-12-22 2012-06-28 Pradeep Iyer HTTP Proxy based Captive Portal
CN102075583A (zh) * 2011-01-30 2011-05-25 杭州华三通信技术有限公司 一种http请求报文处理方法及其设备
CN102868758A (zh) * 2012-09-29 2013-01-09 华为技术有限公司 门户推送的方法和网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2894833A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3128713A1 (en) * 2014-04-04 2017-02-08 ZTE Corporation Page push method, device and server, and centralized network management controller
EP3128713A4 (en) * 2014-04-04 2017-04-05 ZTE Corporation Page push method, device and server, and centralized network management controller

Also Published As

Publication number Publication date
EP2894833A1 (en) 2015-07-15
CN102868758A (zh) 2013-01-09
CN102868758B (zh) 2016-12-21
EP2894833A4 (en) 2015-09-16
US9794362B2 (en) 2017-10-17
EP2894833B1 (en) 2017-05-10
US20150195370A1 (en) 2015-07-09

Similar Documents

Publication Publication Date Title
WO2014048255A1 (zh) 门户推送的方法和网络设备
CN106131079B (zh) 一种认证方法、系统及代理服务器
JP3526435B2 (ja) ネットワークシステム
US9179314B2 (en) Secure and automatic connection to wireless network
CN108496380B (zh) 服务器和存储介质
US20080301303A1 (en) Virtual network connection apparatus, system, method for controlling connection of a virtual network and computer-readable storage medium
WO2013159576A1 (zh) 接入无线网络的方法、终端、wi-fi接入网节点和鉴权服务器
CN103369531B (zh) 一种基于终端信息进行权限控制的方法及装置
WO2017177691A1 (zh) 一种入口认证方法和系统
US8171541B2 (en) Enabling provider network inter-working with mobile access
GB2554953A (en) Improvements in and relating to network communications
JP2009100064A (ja) 無線lanの通信方法及び通信システム
WO2018196633A1 (zh) 路由控制
CN112839331A (zh) 一种用于无线局域网Portal认证逃生的用户信息认证方法
JP7135206B2 (ja) アクセス認証
CN109495362B (zh) 一种接入认证方法及装置
CN109379339B (zh) 一种Portal认证方法及装置
US10505913B2 (en) Communication management system, access point, communication management device, connection control method, communication management method, and program
CA3040804C (en) Portal aggregation service mapping subscriber device identifiers to portal addresses to which connection and authentication requests are redirected and facilitating mass subscriber apparatus configuration
KR20120044381A (ko) 신원과 위치 정보가 분리된 네트워크에서 사용자가 icp 웹사이트에 로그인 하는 방법, 시스템 및 로그인 장치
WO2017181407A1 (zh) 一种网络认证方法、客户端、终端设备及平台
CN105790944A (zh) 一种基于微信的网络认证方法及装置
CN109462568B (zh) Portal认证方法、系统和Portal代理服务器
CN105704105B (zh) 一种认证方法及接入设备
JP6314500B2 (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: 13841686

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2013841686

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2013841686

Country of ref document: EP