WO2017167130A1 - 一种路由方法及装置 - Google Patents

一种路由方法及装置 Download PDF

Info

Publication number
WO2017167130A1
WO2017167130A1 PCT/CN2017/078046 CN2017078046W WO2017167130A1 WO 2017167130 A1 WO2017167130 A1 WO 2017167130A1 CN 2017078046 W CN2017078046 W CN 2017078046W WO 2017167130 A1 WO2017167130 A1 WO 2017167130A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
server cluster
access request
attribute information
attribute
Prior art date
Application number
PCT/CN2017/078046
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 JP2018551227A priority Critical patent/JP6687755B2/ja
Priority to EP17773160.1A priority patent/EP3422672B1/en
Priority to ES17773160T priority patent/ES2828900T3/es
Publication of WO2017167130A1 publication Critical patent/WO2017167130A1/zh
Priority to US16/140,825 priority patent/US11165885B2/en

Links

Images

Classifications

    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/308—Route determination based on user's profile, e.g. premium users
    • 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/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • 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/2866—Architectures; Arrangements
    • H04L67/30—Profiles
    • H04L67/306—User profiles
    • 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/535—Tracking the activity of the user

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a routing method and apparatus.
  • User routing means that when a user accesses a server on a website, the server can forward or proxy the user's access to another suitable server to process the user's request.
  • advanced users such as paying members
  • this requires different levels of users. Route to different servers or server clusters to ensure that key resources are invested in key users, so that when the server resources are bottlenecked, the functions of advanced users can be guaranteed as unaffected as possible.
  • Internet companies that provide user services worldwide are often faced with issues such as privacy and legal protection. For example, country A requires its user data to remain in domestic or politically neutral countries, and country B requires users to retain their user data. Several areas, and so on, also need to route different users to the server cluster in the compliant area.
  • an IP address-based DNS Domain Name System
  • IP address-based DNS Domain Name System
  • the drawback of this scheme is that the distinction of users only depends on the IP address, and the IP address of the user is often not accurate enough, and the classification of the user is usually complicated, only by IP. It is also difficult for the address to make a detailed distinction between users, and it cannot meet the needs of user level distinction, privacy, legal protection, and so on.
  • the present invention provides a routing method and apparatus to achieve more refined user routing.
  • a routing method comprising:
  • Routing the access request to the server cluster Routing the access request to the server cluster.
  • the specific page includes a page to be routed or a page to be provided with a differentiated service.
  • the obtaining the user attribute information of the user based on the access request includes:
  • the obtaining the user identifier includes:
  • the user identifier is obtained in a unified access layer of HTTP.
  • the acquiring the user identifier of the user includes:
  • the user attribute information includes at least one of the following:
  • the user's level attribute, the user's national attribute, the user's country attribute, the user's gender attribute, the user's age attribute, the user's geographic attribute, and the user's historical behavior data are used.
  • the obtaining, according to the user attribute information, the server cluster corresponding to the user attribute information, according to the preset rule includes:
  • the calculating is performed according to the attribute value in the user attribute information, and acquiring the corresponding server cluster according to the calculation result, including:
  • the corresponding server cluster is determined according to the result of the weighting calculation.
  • routing the access request to the server cluster includes:
  • the access request is routed to the server cluster using a redirect.
  • the using the redirection manner to route the access request to the server cluster including:
  • the access request is sent to the server cluster by using a redirect mode of the Http state 302 or 301;
  • the access request is forwarded to the server cluster using a redirect mode of the Http state 308 or 307.
  • the server cluster includes one server or at least two servers.
  • the server cluster is located in a country and/or region specified by a country where the user is located.
  • the server cluster provides differentiated user services.
  • a routing apparatus comprising:
  • An access request receiving unit configured to receive an access request of the user, where the access request points to a specific page
  • a user attribute information obtaining unit configured to acquire user attribute information of the user based on the access request
  • a target server obtaining unit configured to refer to the pre- at least partially according to the user attribute information Setting a rule, obtaining a server cluster corresponding to the user attribute information, where the server cluster is configured to provide a service of the specific page to a user;
  • An access request routing unit is configured to route the access request to the server cluster.
  • the specific page includes a page to be routed or a page to be provided with a differentiated service.
  • the user attribute information acquiring unit includes:
  • a user identifier obtaining subunit configured to acquire a user identifier of the user based on the access request
  • the user attribute information obtaining subunit is configured to acquire user attribute information of the user according to the user identifier.
  • the user identifier obtaining subunit is configured to:
  • the user identifier is obtained in a unified access layer of HTTP.
  • the user identifier obtaining subunit is configured to:
  • the user attribute information includes at least one of the following:
  • the user's level attribute, the user's national attribute, the user's country attribute, the user's gender attribute, the user's age attribute, the user's geographic attribute, and the user's historical behavior data are used.
  • the target server obtaining unit includes:
  • Querying a sub-unit configured to query a preset user attribute and a server correspondence table according to the user attribute information, and obtain the corresponding server cluster according to the query result;
  • the calculating subunit is configured to perform calculation according to the attribute value in the user attribute information, and obtain the corresponding server cluster according to the calculation result.
  • the calculating subunit is configured to: obtain weights of each user attribute, perform weighting calculation according to the weights, and determine the corresponding server cluster according to the result of the weighting calculation.
  • the access request routing unit is configured to:
  • the access request is routed to the server cluster using a redirect.
  • the access request routing unit includes:
  • a first jump subunit configured to: when the access request is a stateless request, use the redirect mode of the Http state 302 or 301 to send the access request to the server cluster;
  • the second jump subunit is configured to, when the access request is a stateful request, use the redirect mode of the Http state 308 or 307 to send the access request to the server cluster.
  • the server cluster includes one server or at least two servers.
  • the server cluster is located in a country and/or region specified by a country where the user is located.
  • the server cluster provides differentiated user services.
  • the user attribute information is first obtained, and then the server cluster to be accessed is determined according to the user attribute information, because complex definitions can be performed in the user attribute information, and complex rule judgments are added, so that the user can be finely routed.
  • the user route of various dimensions and functions can be implemented by using the solution of the invention.
  • the DNS technology has a multi-level DNS cache, and its convergence time is long, generally hourly, and cannot be real-time.
  • user attribute information and judgment rules can be modified at any time, so that user route changes can also be implemented. Real-time, such as when a non-paid user pays, the system can immediately route its access to a server cluster of high stability to provide a higher quality service.
  • FIG. 1 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 2 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 3 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 4 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 5 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 6 is a schematic diagram of a routing scenario according to an exemplary embodiment
  • FIG. 7 is a schematic diagram of a routing scenario according to an exemplary embodiment
  • FIG. 8 is a flowchart of a routing method according to an exemplary embodiment
  • FIG. 9 is a block diagram of a routing apparatus according to an exemplary embodiment.
  • FIG. 10 is a block diagram of a routing apparatus according to an exemplary embodiment
  • FIG. 11 is a block diagram of a routing device, according to an exemplary embodiment.
  • FIG. 1 is a flow chart showing a routing method according to an exemplary embodiment. This method can be used for devices on the network side, such as servers.
  • the method may include steps S101 to S104.
  • Step S101 Receive an access request of a user, where the access request points to a specific page.
  • the specific page may be a page to be routed or a page to be provided with a differentiated service, such as a page where different users display different content, or although the content is the same but It is a page with different speeds and stability, and so on.
  • a differentiated service such as a page where different users display different content, or although the content is the same but It is a page with different speeds and stability, and so on.
  • the invention realizes the differentiation by routing user of different types and levels to a server cluster exhibiting different content through user attribute information, and can also be routed to the server in the country according to the country where the user is located, thereby realizing privacy protection.
  • Step S102 Acquire user attribute information of the user based on the access request.
  • the access request already carries some attribute information of the user.
  • the access request usually includes the browser version information (such as Simplified Chinese, Traditional Chinese, Japanese). , Korean and other language versions), this information can be used to infer the region where the user is located, so at this time, the user's attribute information can be obtained directly from the access request.
  • the browser version information such as Simplified Chinese, Traditional Chinese, Japanese. , Korean and other language versions
  • the acquiring the user attribute information of the user based on the access request may include:
  • Step S201 Acquire a user identifier of the user based on the access request.
  • the embodiment of the user identification of how to obtain the user is not limited.
  • the user identifier of the user may be obtained from a user cookie (login information), where the user identifier is Write the cookie.
  • User IDs can also be referred to as user IDs. For example, after the user logs in with the user ID, the user ID can be written into the cookie in the unified access layer. When you need to get the user ID, you can get it from the cookie.
  • the unified access layer is the entry of each or a group of webpage programs.
  • the access layer is a software that supports the HTTP protocol and a server that runs.
  • all web page requests for external services are from the same access layer, that is, unified access layer. enter.
  • the obtaining the user identifier may include:
  • the user identifier is obtained in a unified access layer of HTTP.
  • the obtaining the user identifier of the user may include:
  • Step S202 Acquire user attribute information of the user according to the user identifier.
  • the user attribute information may be a user's profile.
  • the corresponding user profile can be found in the database or other medium according to the user ID.
  • Step S103 Obtain a server cluster corresponding to the user attribute information according to the user attribute information, and refer to a preset rule, where the server cluster is configured to provide a service of the specific page to a user.
  • the server cluster can include one server or at least two servers.
  • the server cluster may be located in a country and/or region designated by the country in which the user is located.
  • the server cluster can provide differentiated user services.
  • the differentiated services involved in the present invention may also refer to bandwidth enhancement, security enhancement, and the like.
  • Step S104 routing the access request to the server cluster.
  • the information in the profile can be input as a rule, the cluster that the user should access is obtained by calculation, and the user request is redirected or proxyed to the corresponding cluster based on different request types.
  • the specific content of the user attribute information is not limited in the embodiment, and the specific content can be customized by the skilled person, and the specific content can be used herein without departing from the spirit and scope of the invention.
  • the user attribute information includes at least one of the following:
  • the user's level attribute, the user's national attribute, the user's country attribute, the user's gender attribute, the user's age attribute, the user's geographic attribute, and the user's historical behavior data are used.
  • the server cluster corresponding to the user attribute information is obtained by referring to a preset rule according to the user attribute information, at least in part.
  • Step S301 Query a preset user attribute and a server correspondence table according to the user attribute information.
  • a correspondence table between a user country attribute and a server may be preset, and a server or a server cluster to which a country user should be routed may be determined by looking up a table.
  • Step S302 Acquire the corresponding server cluster according to the query result.
  • Step S401 performing calculation according to the attribute value in the user attribute information.
  • each user attribute may be given a certain weight, and then a weighting calculation is performed to determine which server or server cluster should be routed based on the comparison of the weighted calculated score result with a certain threshold.
  • Step S402 Acquire the corresponding server cluster according to the calculation result.
  • the calculating, according to the attribute value in the user attribute information, and acquiring the corresponding server cluster according to the calculation result may include:
  • Step S501 obtaining weights of each user attribute.
  • Step S502 performing weighting calculation according to the weight.
  • Step S503 determining the corresponding server cluster according to the result of the weighting calculation.
  • the routing the access request to the server cluster may include:
  • the access request is routed to the server cluster using a redirect.
  • routing the access request to the server cluster using a redirection manner may include:
  • the access request is sent to the server cluster by using a redirect mode of the Http state 302 or 301;
  • the access request is forwarded to the server cluster using a redirect mode of the Http state 308 or 307.
  • HTTP status code 301 represents permanent movement, it means that the requested resource has been permanently moved to a new location.
  • Status code 302 represents a temporary move, meaning that the server is currently responding to requests from web pages at different locations, but the requestor should continue to use the original location to respond to future requests.
  • Status code 307 represents a temporary redirect, meaning that the currently requested resource should be resent by another address, however future requests should still use the original address.
  • Status code 308 represents permanent transfer, referring to The requested resource will be permanently located at another address, which means that both the current request and the subsequent request should be resent by another address.
  • different processing methods may be used for different types of requests. For example, when a user requests a stateless request, such as a GET request, in order to reduce inter-server dependencies, 302 or 301 may be used to cause the browser to jump to the corresponding server cluster; and if it is a stateful request such as a POST or PUT request, Similarly, in order to reduce the call between servers, the 308 or 307 jump can be used to jump to the corresponding server cluster, and the jump will carry the data submitted in the user form, so that the user function is not affected at all.
  • a stateless request such as a GET request
  • 302 or 301 may be used to cause the browser to jump to the corresponding server cluster; and if it is a stateful request such as a POST or PUT request.
  • the 308 or 307 jump can be used to jump to the corresponding server cluster, and the jump will carry the data submitted in the user form, so that the user function is not affected at all.
  • the user attribute information is first obtained, and then the server cluster to be accessed is determined according to the user attribute information, because complex definitions can be performed in the user attribute information, and complex rule judgments are added, so that the user can be refined when routing.
  • the user route with various dimensions and functions can be implemented by using the solution of the invention.
  • the DNS technology has a multi-level DNS cache, and its convergence time is long, generally hourly, and cannot be real-time.
  • user attribute information and judgment rules can be modified at any time, so that user route changes can also be implemented. Real-time, such as when a non-paid user pays, the system can immediately route its access to a server cluster of high stability to provide a higher quality service.
  • a free user accesses a page requiring user routing through a terminal device 601 (such as a laptop), and the server 602 routes it to the server 603 according to the user ID to complete the access.
  • a terminal device 601 such as a laptop
  • a paying user accesses the same page that needs to be routed by the user through the terminal device 701 (such as a mobile phone), and the server 602 routes it to the server 604 according to the user ID to complete the access.
  • the terminal device 701 such as a mobile phone
  • step S801 the user logs in.
  • step S802 the server writes the user ID into the cookie.
  • Step S803 the user accesses a page that needs to perform user routing.
  • step S804 the server acquires the user ID according to the cookie.
  • Step S805 the corresponding user profile is read from the database according to the user ID.
  • Step S807 calculating a target server cluster to be routed according to the information in the user profile.
  • step S807 it is determined whether the user's request is a stateful request. If it is a stateful request, it proceeds to step S808, and if it is a stateless request, it proceeds to step S809.
  • Steps S808, 308/307 jump to the target server cluster. The process ends.
  • Steps S809, 302/301 jump to the target server cluster. The process ends.
  • the user attribute information is first obtained by using the user identifier, and then the server or server cluster to be accessed is determined according to the user attribute information, because complex definitions can be performed in the user attribute information, and complex rule judgments are added, so that the user routes
  • the time can be finely distinguished, so that the user route with various dimensions and functions can be implemented by using the solution of the present invention.
  • the DNS technology has a multi-level DNS cache, and its convergence time is long, generally hourly, and cannot be real-time.
  • user attribute information and judgment rules can be modified at any time, so that user route changes can also be implemented. Real-time, such as when a non-paid user pays, the system can immediately route its access to a server cluster of high stability to provide a higher quality service.
  • FIG. 9 is a block diagram of a routing device, according to an exemplary embodiment.
  • the device can be used for devices on the network side, such as servers.
  • the apparatus can include:
  • the access request receiving unit 901 is configured to receive an access request of the user, where the access request points to a specific page.
  • the user attribute information obtaining unit 902 is configured to acquire user attribute information of the user based on the access request.
  • the target server obtaining unit 903 is configured to obtain, according to the user attribute information, a server cluster corresponding to the user attribute information by referring to a preset rule, where the server cluster is configured to provide a service of the specific page to a user.
  • An access request routing unit 904 is configured to route the access request to the server cluster.
  • the server cluster can include one server or at least two servers.
  • the server cluster may be located in a country and/or region designated by the country in which the user is located.
  • the server cluster can provide differentiated user services.
  • the differentiated services involved in the present invention may also refer to bandwidth enhancement, security enhancement, and the like.
  • the specific page includes a page to be routed or a page to be provided with a differentiated service.
  • the user attribute information acquiring unit includes:
  • a user identifier obtaining subunit 1001, configured to acquire a user identifier of the user based on the access request
  • the user attribute information obtaining subunit 1002 is configured to acquire user attribute information of the user according to the user identifier.
  • the user identifier obtaining subunit is configured to:
  • the user identifier is obtained in a unified access layer of HTTP.
  • the user identifier obtaining subunit is configured to:
  • the user attribute information may include at least one of the following:
  • the user's level attribute, the user's national attribute, the user's country attribute, the user's gender attribute, the user's age attribute, the user's geographic attribute, and the user's historical behavior data are used.
  • the target server obtaining unit may include:
  • Querying a sub-unit configured to query a preset user attribute and a server correspondence table according to the user attribute information, and obtain the corresponding server cluster according to the query result;
  • the calculating subunit is configured to perform calculation according to the attribute value in the user attribute information, and obtain the corresponding server cluster according to the calculation result.
  • calculation subunit is used to:
  • the access request routing unit may be used to:
  • the access request is routed to the server cluster using a redirect.
  • the access request routing unit may include:
  • the first jump subunit 1101 is configured to: when the access request is a stateless request, use the redirect mode of the Http state 302 or 301 to send the access request to the server cluster.
  • the second jump subunit 1102 is configured to: when the access request is a stateful request, use the redirect mode of the Http state 308 or 307 to send the access request to the server cluster.
  • the user attribute information is first obtained, and then the server cluster to be accessed is determined according to the user attribute information, because complex definitions can be performed in the user attribute information, and complex rule judgments are added, so that the user can be refined when routing.
  • the user route with various dimensions and functions can be implemented by using the solution of the invention.
  • DNS technology has The multi-level DNS cache has a long convergence time, generally an hourly level, and cannot be real-time.
  • the user attribute information and the judgment rule can be modified at any time, so that the user route can also be changed in real time, for example, non-paid. Once the user pays, the system can immediately route its access to a server cluster of high stability to provide a higher quality service.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明实施例提供了一种路由方法及装置，其中方法包括：接收用户的访问请求，其中所述访问请求指向特定页面；基于所述访问请求，获取所述用户的用户属性信息；至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务；将所述访问请求路由到所述服务器集群。在本发明实施例中，先获取用户属性信息，然后根据用户属性信息确定要访问的服务器集群，因为在用户属性信息中可以进行复杂的定义以及加入复杂的规则判断，使得用户路由时可以被精细化区分，故利用本发明的方案可以实施各种维度、功能非常丰富的用户路由。

Description

一种路由方法及装置 技术领域
本发明涉及通信技术领域，尤其涉及一种路由方法及装置。
背景技术
用户路由是指当用户访问网站的某台服务器时，这台服务器可以将用户的访问转发或代理到其他合适的服务器以处理该用户的请求。随着互联网的发展，很多公司开始尝试对用户进行分级，实行区别对待，达到对高级用户(例如付费会员)提供更高质量的服务等目的，从技术上讲，这就需要将不同等级的用户路由到不同的服务器或服务器集群中，保证重点资源投入到重点用户，以便当服务器资源出现瓶颈时可以保证高级用户的功能尽可能不受到影响。此外，对于提供全球范围内用户服务的互联网公司，往往会面临隐私\法律保护等问题，例如A国家要求其用户数据必须留在国内或政治中立国家，B国家用户要求其用户数据必须留在指定的几个区域，等等，此时也需要将不同用户路由到合规区域内的服务器集群中。
在现有技术中，利用基于IP地址的DNS(Domain Name System，域名***)技术，可以在不同用户访问同一域名时，根据用户的IP地址将用户路由到特定的服务器集群。然而，发明人在实现本发明的过程中发现，这种方案的缺陷在于对用户的区分仅仅依靠IP地址，而用户的IP地址往往是不够准确的，并且用户的分类通常很复杂，仅凭IP地址也很难做到对用户进行详细的区分，无法满足用户级别区分、隐私\法律保护等多方面的需求。
发明内容
为克服现有技术中存在的问题，本发明提供一种路由方法及装置，以实现更精细化的用户路由。
根据本发明实施例的第一方面，提供一种路由方法，所述方法包括：
接收用户的访问请求，其中所述访问请求指向特定页面；
基于所述访问请求，获取所述用户的用户属性信息；
至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务；
将所述访问请求路由到所述服务器集群。
可选的，所述特定页面包括有待进行路由的页面或有待提供差异化服务的页面。
可选的，所述基于所述访问请求，获取所述用户的用户属性信息，包括：
基于所述访问请求，获取所述用户的用户标识；
根据所述用户标识，获取所述用户的用户属性信息。
可选的，所述获取所述用户标识，包括：
在HTTP的统一接入层中获取所述用户标识。
可选的，所述获取所述用户的用户标识，包括：
从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
可选的，所述用户属性信息包括以下至少一项：
用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
可选的，所述至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，包括：
根据所述用户属性信息查询预设的用户属性与服务器集群对应表；
根据查询结果获取所述对应的服务器集群；
或者，
根据所述用户属性信息中的属性值进行计算；
根据计算结果获取所述对应的服务器集群。
可选的，所述根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群，包括：
获取每个用户属性的权重：
根据所述权重进行加权计算；
根据加权计算的结果确定所述对应的服务器集群。
可选的，所述将所述访问请求路由到所述服务器集群，包括：
使用重定向方式将所述访问请求路由到所述服务器集群。
可选的，所述使用重定向方式将所述访问请求路由到所述服务器集群，包括：
当所述访问请求为无状态请求时，采用Http状态302或301的重定向方式将所述访问请求至所述服务器集群；
当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
可选的，所述服务器集群包括一台服务器或至少两台服务器。
可选的，所述服务器集群位于所述用户的所在国家所指定的国家和/或地区内。
可选的，所述服务器集群提供差异化的用户服务。
根据本发明实施例的第二方面，提供一种路由装置，所述装置包括：
访问请求接收单元，用于接收用户的访问请求，其中所述访问请求指向特定页面；
用户属性信息获取单元，用于基于所述访问请求，获取所述用户的用户属性信息；
目标服务器获取单元，用于至少部分根据所述用户属性信息，参照预 设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务；
访问请求路由单元，用于将所述访问请求路由到所述服务器集群。
可选的，所述特定页面包括有待进行路由的页面或有待提供差异化服务的页面。
可选的，所述用户属性信息获取单元包括：
用户标识获取子单元，用于基于所述访问请求，获取所述用户的用户标识；
用户属性信息获取子单元，用于根据所述用户标识，获取所述用户的用户属性信息。
可选的，所述用户标识获取子单元用于：
在HTTP的统一接入层中获取所述用户标识。
可选的，所述用户标识获取子单元用于：
从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
可选的，所述用户属性信息包括以下至少一项：
用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
可选的，所述目标服务器获取单元包括：
查询子单元，用于根据所述用户属性信息查询预设的用户属性与服务器对应表，根据查询结果获取所述对应的服务器集群；
或者包括：
计算子单元，用于根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群。
可选的，所述计算子单元用于：获取每个用户属性的权重，根据所述权重进行加权计算，根据加权计算的结果确定所述对应的服务器集群。
可选的，所述访问请求路由单元用于：
使用重定向方式将所述访问请求路由到所述服务器集群。
可选的，所述访问请求路由单元包括：
第一跳转子单元，用于当所述访问请求为无状态请求时，采用Http状态302或301的重定向方式将所述访问请求至所述服务器集群；
第二跳转子单元，用于当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
可选的，所述服务器集群包括一台服务器或至少两台服务器。
可选的，所述服务器集群位于所述用户的所在国家所指定的国家和/或地区内。
可选的，所述服务器集群提供差异化的用户服务。
本发明的实施例提供的技术方案可以包括以下有益效果：
在本发明实施例中，先获取用户属性信息，然后根据用户属性信息确定要访问的服务器集群，因为在用户属性信息中可以进行复杂的定义以及加入复杂的规则判断，使得用户路由时可以被精细化区分，故利用本发明的方案可以实施各种维度、功能非常丰富的用户路由。此外，DNS技术由于有多级DNS缓存，其收敛时间较长，一般是小时级别，无法做到实时性，而本发明中用户属性信息及判断规则可以随时修改，这样用户路由变更起来也可以实现实时性，例如非付费用户一旦付费，***便可以立即将其访问路由到稳定性级别高的服务器集群中以提供更高质量的服务。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本发明。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明的实施例，并与说明书一起用于解释本发明的原理。
图1是根据一示例性实施例示出的一种路由方法的流程图；
图2是根据一示例性实施例示出的一种路由方法的流程图；
图3是根据一示例性实施例示出的一种路由方法的流程图；
图4是根据一示例性实施例示出的一种路由方法的流程图；
图5是根据一示例性实施例示出的一种路由方法的流程图；
图6是根据一示例性实施例示出的路由场景示意图；
图7是根据一示例性实施例示出的路由场景示意图；
图8是根据一示例性实施例示出的一种路由方法的流程图；
图9是根据一示例性实施例示出的一种路由装置的框图；
图10是根据一示例性实施例示出的一种路由装置的框图；
图11是根据一示例性实施例示出的一种路由装置的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明的一些方面相一致的装置和方法的例子。
图1是根据一示例性实施例示出的一种路由方法的流程图。该方法可以用于网络侧的设备，如服务器。
参见图1所示，该方法可以包括步骤S101～S104。
步骤S101，接收用户的访问请求，其中所述访问请求指向特定页面。
其中作为示例，特定页面可以是有待进行路由的页面或有待提供差异化服务的页面，例如不同用户展示不同内容的页面，或者虽然内容相同但 是速度\稳定性不同的页面，等等。当用户在访问这些需要进行用户路由的页面时，网络会将该用户路由到合适的服务器或服务器集群以实现访问。
例如某网站上有来自于全世界的买家，如何保护买家隐私不会泄漏，如何做到将买家信息只保留在其国内，是一个需要解决的问题。本发明通过用户属性信息，将不同类型\级别等的用户路由到展现不同内容的服务器集群来实现差异化，还可以基于用户所在国家，将其路由到其国内的服务器中，从而实现隐私保护。
步骤S102，基于所述访问请求，获取所述用户的用户属性信息。
作为示例，在一些情形下，访问请求中已携带用户的某种属性信息，例如用户通过浏览器发送访问请求时，访问请求中通常会含有浏览器的版本信息(如简体中文、繁体中文、日文、韩文等语言版本)，通过该信息就可以推断出用户所处的地域，所以此时便可以直接从访问请求中获取用户的属性信息。
而在另外一些情形下，参见图2所示，在本实施例或本发明其他某些实施例中，所述基于所述访问请求，获取所述用户的用户属性信息，可以包括：
步骤S201，基于所述访问请求，获取所述用户的用户标识。
对于如何获取用户的用户标识本实施例并不进行限制。在本实施例或本发明其他某些实施例中，当需要获取用户标识时，可以从用户Cookie(登录信息)中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述Cookie。
用户标识也可称为用户ID。例如在用户以用户ID登录后，可以在统一接入层中将用户ID写入Cookie。当需要获取用户ID时，从Cookie中获取即可。
统一接入层即每一个或一组网页程序的入口，对于网页程序，接入层是部署支持HTTP协议的软件及其运行的服务器。例如可使用Nginx、Apache、Jetty、Tomcat等服务器，只需要支持HTTP协议即可。对于一个大型网站，所有对外提供服务的网页请求都从同一个接入层即统一接入层 进入。
换句话说，所述获取所述用户标识，可以包括：
在HTTP的统一接入层中获取所述用户标识。
从另一个角度来讲，所述获取所述用户的用户标识，可以包括：
从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
步骤S202，根据所述用户标识，获取所述用户的用户属性信息。例如用户属性信息可以是用户的Profile(配置文件)。可以根据用户ID在数据库或其它介质中查找到对应的用户Profile。
步骤S103，至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务。
作为示例，所述服务器集群可以包括一台服务器或至少两台服务器。所述服务器集群可位于所述用户的所在国家所指定的国家和/或地区内。
所述服务器集群可提供差异化的用户服务。另外除了提供差异化的网页外，本发明中所涉及的差异化服务也可以是指带宽提升、安全性提升，等等。
步骤S104，将所述访问请求路由到所述服务器集群。
例如可以将Profile内的信息作为规则输入，通过计算得到用户应该访问的集群，并基于不同的请求类型将用户请求重定向或代理到对应的集群中。
对于用户属性信息的具体内容本实施例并不进行限制，技术人员可以根据具体情况进行自定义，可以在此处使用的这些具体内容都没有背离本发明的精神和保护范围。
在本实施例或本发明其他某些实施例中，所述用户属性信息包括以下至少一项：
用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
作为示例可参见表1所示：
表1
Figure PCTCN2017078046-appb-000001
参见图3～4所示，在本实施例或本发明其他某些实施例中，所述至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，可以包括：
步骤S301，根据所述用户属性信息查询预设的用户属性与服务器对应表。
作为示例，可以预设用户国别属性与服务器的对应表，通过查表确定某国别的用户应该路由到哪个服务器或服务器集群。
步骤S302，根据查询结果获取所述对应的服务器集群。
或者包括：
步骤S401，根据所述用户属性信息中的属性值进行计算。
作为示例，可以为每个用户属性赋予一定的权重，然后进行加权计算，根据加权计算的分数结果与某阈值的比较，确定应该路由到哪个服务器或服务器集群。
步骤S402，根据计算结果获取所述对应的服务器集群。
作为示例可参见图5所示，所述根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群，可以包括：
步骤S501，获取每个用户属性的权重。
步骤S502，根据所述权重进行加权计算。
步骤S503，根据加权计算的结果确定所述对应的服务器集群。
在本实施例或本发明其他某些实施例中，所述将所述访问请求路由到所述服务器集群，可以包括：
使用重定向方式将所述访问请求路由到所述服务器集群。
作为示例，使用重定向方式将所述访问请求路由到所述服务器集群，可以包括：
当所述访问请求为无状态请求时，采用Http状态302或301的重定向方式将所述访问请求至所述服务器集群；
当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
简单来讲，其中HTTP状态码301代表永久移动，指所请求的资源已永久移动到新位置。状态码302代表临时移动，指服务器目前从不同位置的网页响应请求，但请求者应继续使用原有位置来响应以后的请求。状态码307代表临时重定向，指当前所请求的资源应该被另一个地址重新发送，然而未来的请求仍然应该使用原始的地址。状态码308代表永久转移，指 所请求的资源将永久的位于另外一个地址上，也即指本次请求和以后的请求都应该被另一个地址重新发送。
在实施时具体来讲，根据规则计算得到用户服务器集群后，对于不同类型的请求可以有不同的处理方法。例如当用户请求为无状态请求时，如GET请求，为了减少服务器间依赖关系，可采用302或301让浏览器自行跳转至对应服务器集群；而如果是POST或PUT请求等有状态的请求，同样为了减少服务器间的调用，可采用308或307跳转的方式跳转至对应的服务器集群，此时的跳转会将用户表单中提交的数据携带，从而完全不影响用户功能。
在本实施例中，先获取用户属性信息，然后根据用户属性信息确定要访问的服务器集群，因为在用户属性信息中可以进行复杂的定义以及加入复杂的规则判断，使得用户路由时可以被精细化区分，故利用本发明的方案可以实施各种维度、功能非常丰富的用户路由。此外，DNS技术由于有多级DNS缓存，其收敛时间较长，一般是小时级别，无法做到实时性，而本发明中用户属性信息及判断规则可以随时修改，这样用户路由变更起来也可以实现实时性，例如非付费用户一旦付费，***便可以立即将其访问路由到稳定性级别高的服务器集群中以提供更高质量的服务。
下面结合具体场景对本发明方案作进一步描述。
在图6所示的场景中，一免费用户通过终端设备601(如笔记本电脑)访问需要进行用户路由的页面，服务器602根据用户ID将其路由到服务器603以完成访问。
而在图7所示的场景中，一付费用户通过终端设备701(如手机)访问同一需要进行用户路由的页面，服务器602根据用户ID将其路由到服务器604以完成访问。
相关过程可进一步参见图8所示，包括：
步骤S801，用户登录。
步骤S802，服务器将用户ID写入Cookie。
步骤S803，用户访问需要进行用户路由的页面。
步骤S804，服务器根据Cookie获取用户ID。
步骤S805，根据用户ID从数据库中读取到相应的用户Profile。
步骤S807，根据用户Profile中的信息计算出应路由的目标服务器集群。
步骤S807，判断用户的请问是否是有状态请求。如果是有状态请求，则进入步骤S808，如果是无状态请求，则进入步骤S809。
步骤S808，308/307跳转至目标服务器集群。流程结束。
步骤S809，302/301跳转至目标服务器集群。流程结束。
在本实施例中，先通过用户标识获取用户属性信息，然后根据用户属性信息确定要访问的服务器或服务器集群，因为在用户属性信息中可以进行复杂的定义以及加入复杂的规则判断，使得用户路由时可以被精细化区分，故利用本发明的方案可以实施各种维度、功能非常丰富的用户路由。此外，DNS技术由于有多级DNS缓存，其收敛时间较长，一般是小时级别，无法做到实时性，而本发明中用户属性信息及判断规则可以随时修改，这样用户路由变更起来也可以实现实时性，例如非付费用户一旦付费，***便可以立即将其访问路由到稳定性级别高的服务器集群中以提供更高质量的服务。
下述为本发明装置实施例，可以用于执行本发明方法实施例。对于本发明装置实施例中未披露的细节，请参照本发明方法实施例。
图9是根据一示例性实施例示出的一种路由装置的框图。该装置可以用于网络侧的设备，如服务器。
参见图9所示，该装置可以包括：
访问请求接收单元901，用于接收用户的访问请求，其中所述访问请求指向特定页面。
用户属性信息获取单元902，用于基于所述访问请求，获取所述用户的用户属性信息。
目标服务器获取单元903，用于至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务。
访问请求路由单元904，用于将所述访问请求路由到所述服务器集群。
作为示例，所述服务器集群可以包括一台服务器或至少两台服务器。所述服务器集群可位于所述用户的所在国家所指定的国家和/或地区内。
所述服务器集群可提供差异化的用户服务。另外除了提供差异化的网页外，本发明中所涉及的差异化服务也可以是指带宽提升、安全性提升，等等。
在本实施例或本发明其他某些实施例中，所述特定页面包括有待进行路由的页面或有待提供差异化服务的页面。
参见图10所示，在本实施例或本发明其他某些实施例中，所述用户属性信息获取单元包括：
用户标识获取子单元1001，用于基于所述访问请求，获取所述用户的用户标识；
用户属性信息获取子单元1002，用于根据所述用户标识，获取所述用户的用户属性信息。
在本实施例或本发明其他某些实施例中，所述用户标识获取子单元用于：
在HTTP的统一接入层中获取所述用户标识。
在本实施例或本发明其他某些实施例中，所述用户标识获取子单元用于：
从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
在本实施例或本发明其他某些实施例中，所述用户属性信息可以包括以下至少一项：
用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
在本实施例或本发明其他某些实施例中，所述目标服务器获取单元可以包括：
查询子单元，用于根据所述用户属性信息查询预设的用户属性与服务器对应表，根据查询结果获取所述对应的服务器集群；
或者包括：
计算子单元，用于根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群。
作为示例，所述计算子单元用于：
获取每个用户属性的权重，根据所述权重进行加权计算，根据加权计算的结果确定所述对应的服务器集群。
在本实施例或本发明其他某些实施例中，所述访问请求路由单元可以用于：
使用重定向方式将所述访问请求路由到所述服务器集群。
作为示例可参见图11所示，所述访问请求路由单元可以包括：
第一跳转子单元1101，用于当所述访问请求为无状态请求时，采用Http状态302或301的重定向方式将所述访问请求至所述服务器集群。
第二跳转子单元1102，用于当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
在本实施例中，先获取用户属性信息，然后根据用户属性信息确定要访问的服务器集群，因为在用户属性信息中可以进行复杂的定义以及加入复杂的规则判断，使得用户路由时可以被精细化区分，故利用本发明的方案可以实施各种维度、功能非常丰富的用户路由。此外，DNS技术由于有 多级DNS缓存，其收敛时间较长，一般是小时级别，无法做到实时性，而本发明中用户属性信息及判断规则可以随时修改，这样用户路由变更起来也可以实现实时性，例如非付费用户一旦付费，***便可以立即将其访问路由到稳定性级别高的服务器集群中以提供更高质量的服务。
关于上述实施例中的装置，其中各个单元执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本申请旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本发明未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由所附的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (26)

  1. 一种路由方法，其特征在于，所述方法包括：
    接收用户的访问请求，其中所述访问请求指向特定页面；
    基于所述访问请求，获取所述用户的用户属性信息；
    至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务；
    将所述访问请求路由到所述服务器集群。
  2. 根据权利要求1所述的方法，其特征在于，所述特定页面包括有待进行路由的页面或有待提供差异化服务的页面。
  3. 根据权利要求1所述的方法，其特征在于，所述基于所述访问请求，获取所述用户的用户属性信息，包括：
    基于所述访问请求，获取所述用户的用户标识；
    根据所述用户标识，获取所述用户的用户属性信息。
  4. 根据权利要求3所述的方法，其特征在于，所述获取所述用户的用户标识，包括：
    在HTTP的统一接入层中获取所述用户标识。
  5. 根据权利要求3所述的方法，其特征在于，所述获取所述用户的用户标识，包括：
    从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
  6. 根据权利要求1所述的方法，其特征在于，所述用户属性信息包括以下至少一项：
    用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
  7. 根据权利要求1所述的方法，其特征在于，所述至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，包括：
    根据所述用户属性信息查询预设的用户属性与服务器集群对应表；
    根据查询结果获取所述对应的服务器集群；
    或者，
    根据所述用户属性信息中的属性值进行计算；
    根据计算结果获取所述对应的服务器集群。
  8. 根据权利要求7所述的方法，其特征在于，所述根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群，包括：
    获取每个用户属性的权重：
    根据所述权重进行加权计算；
    根据加权计算的结果确定所述对应的服务器集群。
  9. 根据权利要求1所述的方法，其特征在于，所述将所述访问请求路由到所述服务器集群，包括：
    使用重定向方式将所述访问请求路由到所述服务器集群。
  10. 根据权利要求9所述的方法，其特征在于，所述使用重定向方式将所述访问请求路由到所述服务器集群，包括：
    当所述访问请求为无状态请求时，采用Http状态302或301的重定向 方式将所述访问请求至所述服务器集群；
    当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
  11. 根据权利要求1所述的方法，其特征在于，所述服务器集群包括一台服务器或至少两台服务器。
  12. 根据权利要求1所述的方法，其特征在于，所述服务器集群位于所述用户的所在国家所指定的国家和/或地区内。
  13. 根据权利要求1所述的方法，其特征在于，所述服务器集群提供差异化的用户服务。
  14. 一种路由装置，其特征在于，所述装置包括：
    访问请求接收单元，用于接收用户的访问请求，其中所述访问请求指向特定页面；
    用户属性信息获取单元，用于基于所述访问请求，获取所述用户的用户属性信息；
    目标服务器获取单元，用于至少部分根据所述用户属性信息，参照预设规则，获取与所述用户属性信息对应的服务器集群，所述服务器集群用于向用户提供所述特定页面的服务；
    访问请求路由单元，用于将所述访问请求路由到所述服务器集群。
  15. 根据权利要求14所述的装置，其特征在于，所述特定页面包括有待进行路由的页面或有待提供差异化服务的页面。
  16. 根据权利要求14所述的装置，其特征在于，所述用户属性信息获取单元包括：
    用户标识获取子单元，用于基于所述访问请求，获取所述用户的用户标识；
    用户属性信息获取子单元，用于根据所述用户标识，获取所述用户的用户属性信息。
  17. 根据权利要求16所述的装置，其特征在于，所述用户标识获取子单元用于：
    在HTTP的统一接入层中获取所述用户标识。
  18. 根据权利要求16所述的装置，其特征在于，所述用户标识获取子单元用于：
    从用户登录信息中获取所述用户的用户标识，其中所述用户标识在所述用户登录时被写入所述登录信息。
  19. 根据权利要求14所述的装置，其特征在于，所述用户属性信息包括以下至少一项：
    用户的等级属性，用户的民族属性，用户的国别属性，用户的性别属性，用户的年龄属性，用户的地理位置属性，用户的历史行为数据。
  20. 根据权利要求14所述的装置，其特征在于，所述目标服务器获取单元包括：
    查询子单元，用于根据所述用户属性信息查询预设的用户属性与服务器对应表，根据查询结果获取所述对应的服务器集群；
    或者包括：
    计算子单元，用于根据所述用户属性信息中的属性值进行计算，根据计算结果获取所述对应的服务器集群。
  21. 根据权利要求20所述的装置，其特征在于，所述计算子单元用 于：获取每个用户属性的权重，根据所述权重进行加权计算，根据加权计算的结果确定所述对应的服务器集群。
  22. 根据权利要求14所述的装置，其特征在于，所述访问请求路由单元用于：
    使用重定向方式将所述访问请求路由到所述服务器集群。
  23. 根据权利要求22所述的装置，其特征在于，所述访问请求路由单元包括：
    第一跳转子单元，用于当所述访问请求为无状态请求时，采用Http状态302或301的重定向方式将所述访问请求至所述服务器集群；
    第二跳转子单元，用于当所述访问请问为有状态请求时，采用Http状态308或307的重定向方式将所述访问请求至所述服务器集群。
  24. 根据权利要求14所述的装置，其特征在于，所述服务器集群包括一台服务器或至少两台服务器。
  25. 根据权利要求14所述的装置，其特征在于，所述服务器集群位于所述用户的所在国家所指定的国家和/或地区内。
  26. 根据权利要求14所述的装置，其特征在于，所述服务器集群提供差异化的用户服务。
PCT/CN2017/078046 2016-03-31 2017-03-24 一种路由方法及装置 WO2017167130A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2018551227A JP6687755B2 (ja) 2016-03-31 2017-03-24 ルーティング方法及び装置
EP17773160.1A EP3422672B1 (en) 2016-03-31 2017-03-24 Routing method and device
ES17773160T ES2828900T3 (es) 2016-03-31 2017-03-24 Método y dispositivo de enrutamiento
US16/140,825 US11165885B2 (en) 2016-03-31 2018-09-25 Routing method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610197316.3 2016-03-31
CN201610197316.3A CN107295033B (zh) 2016-03-31 2016-03-31 一种路由方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/140,825 Continuation US11165885B2 (en) 2016-03-31 2018-09-25 Routing method and device

Publications (1)

Publication Number Publication Date
WO2017167130A1 true WO2017167130A1 (zh) 2017-10-05

Family

ID=59963467

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078046 WO2017167130A1 (zh) 2016-03-31 2017-03-24 一种路由方法及装置

Country Status (6)

Country Link
US (1) US11165885B2 (zh)
EP (1) EP3422672B1 (zh)
JP (1) JP6687755B2 (zh)
CN (1) CN107295033B (zh)
ES (1) ES2828900T3 (zh)
WO (1) WO2017167130A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737270A (zh) * 2018-05-07 2018-11-02 北京京东尚科信息技术有限公司 一种服务器集群的资源管理方法和装置
JP2020027369A (ja) * 2018-08-09 2020-02-20 株式会社エヌケービー 広告配信システム、コンピュータの動作方法、及びクラウドサーバ

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107819687A (zh) * 2017-11-15 2018-03-20 小草数语（北京）科技有限公司 固定路由方法、装置及其设备
CN108111595A (zh) * 2017-12-18 2018-06-01 北京安博通科技股份有限公司 一种服务器负载的均衡方法及装置
CN108667934A (zh) * 2018-05-11 2018-10-16 中国平安人寿保险股份有限公司 信息处理方法、装置、电子设备及存储介质
CN109151022B (zh) * 2018-08-21 2022-06-14 平安科技（深圳）有限公司 网页控制台的调用方法、装置、计算机设备及存储介质
CN109558560B (zh) * 2018-11-30 2021-06-15 象山邱工联信息技术有限公司 基于云数据管理的集群网站管理***
CN111209107A (zh) * 2019-12-26 2020-05-29 中科曙光国际信息产业有限公司 多集群操作方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729591A (zh) * 2008-10-29 2010-06-09 ***通信集团公司 一种用户引导装置、***和方法
CN102497402A (zh) * 2011-12-01 2012-06-13 深圳市同洲视讯传媒有限公司 一种内容注入方法及***、内容分发方法及***
CN103685609A (zh) * 2013-12-25 2014-03-26 乐视网信息技术（北京）股份有限公司 域名解析中路由配置信息采集方法及装置
CN103825975A (zh) * 2014-02-26 2014-05-28 北京太阳庄科技有限公司 Cdn节点分配服务器及***

Family Cites Families (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5893117A (en) 1990-08-17 1999-04-06 Texas Instruments Incorporated Time-stamped database transaction and version management system
US6532493B1 (en) 1998-10-29 2003-03-11 Cisco Technology, Inc. Methods and apparatus for redirecting network cache traffic
CA2388628C (en) 1999-10-22 2010-12-14 Nomadix,Inc. Systems and methods for providing dynamic network authorization, authentication and accounting
US20020131075A1 (en) 2000-05-17 2002-09-19 Heidelberg Digital L.L.C.. Tab modification system for a printing machine
US20020198937A1 (en) 2001-03-09 2002-12-26 Arif Diwan Content-request redirection method and system
US20030014539A1 (en) 2001-06-12 2003-01-16 Reznick Josh L. System and method for traffic management
JP2003216608A (ja) 2002-01-23 2003-07-31 Sony Corp 情報収集／分析方法及びシステム
US7136922B2 (en) 2002-10-15 2006-11-14 Akamai Technologies, Inc. Method and system for providing on-demand content delivery for an origin server
US20050105513A1 (en) 2002-10-27 2005-05-19 Alan Sullivan Systems and methods for direction of communication traffic
US7353070B2 (en) 2003-09-25 2008-04-01 Siemens Building Technologies, Inc. Building control system using network global data
US8590032B2 (en) * 2003-12-10 2013-11-19 Aventail Llc Rule-based routing to resources through a network
US8255973B2 (en) 2003-12-10 2012-08-28 Chris Hopen Provisioning remote computers for accessing resources
US7493414B2 (en) 2004-04-20 2009-02-17 The Boeing Company Apparatus and methods relating to web browser redirection
US9009313B2 (en) * 2004-07-12 2015-04-14 NetSuite Inc. Simultaneous maintenance of multiple versions of a web-based business information system
US9020887B2 (en) 2004-12-21 2015-04-28 Proofpoint, Inc. Managing the status of documents in a distributed storage system
AU2006251563A1 (en) * 2005-05-24 2006-11-30 Paxfire, Inc. Enhanced features for direction of communication traffic
US8271967B2 (en) 2008-06-09 2012-09-18 Ricoh Company, Ltd. MFP software update using web service
US8612862B2 (en) 2008-06-27 2013-12-17 Microsoft Corporation Integrated client for access to remote resources
US9137209B1 (en) 2008-12-10 2015-09-15 Amazon Technologies, Inc. Providing local secure network access to remote services
US8218553B2 (en) 2009-02-25 2012-07-10 Juniper Networks, Inc. Load balancing network traffic on a label switched path using resource reservation protocol with traffic engineering
US8259585B1 (en) 2009-04-17 2012-09-04 Juniper Networks, Inc. Dynamic link load balancing
US9009330B2 (en) * 2010-04-01 2015-04-14 Cloudflare, Inc. Internet-based proxy service to limit internet visitor connection speed
US8843160B2 (en) 2010-12-23 2014-09-23 International Business Machines Corporation Location based wireless tower caching
US8612284B1 (en) * 2011-11-09 2013-12-17 Parallels IP Holdings GmbH Quality of service differentiated cloud storage
US20140032552A1 (en) * 2012-07-30 2014-01-30 Ira Cohen Defining relationships
US8782683B2 (en) * 2012-10-12 2014-07-15 At&T Intellectual Property I, Lp Method and apparatus for managing advertising
US9860316B2 (en) * 2014-09-19 2018-01-02 Facebook, Inc. Routing network traffic based on social information
CN106933548B (zh) * 2015-12-29 2021-01-12 阿里巴巴集团控股有限公司 全局信息获取、处理及更新、方法、装置和***
US10079877B2 (en) * 2016-02-04 2018-09-18 Citrix Systems, Inc. System and method for cloud aware application delivery controller
US10015086B2 (en) * 2016-04-29 2018-07-03 Intuit Inc. Multi GTM based routing to avoid latencies
US20180139273A1 (en) * 2016-11-14 2018-05-17 Linkedin Corporation Entity based routing

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729591A (zh) * 2008-10-29 2010-06-09 ***通信集团公司 一种用户引导装置、***和方法
CN102497402A (zh) * 2011-12-01 2012-06-13 深圳市同洲视讯传媒有限公司 一种内容注入方法及***、内容分发方法及***
CN103685609A (zh) * 2013-12-25 2014-03-26 乐视网信息技术（北京）股份有限公司 域名解析中路由配置信息采集方法及装置
CN103825975A (zh) * 2014-02-26 2014-05-28 北京太阳庄科技有限公司 Cdn节点分配服务器及***

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108737270A (zh) * 2018-05-07 2018-11-02 北京京东尚科信息技术有限公司 一种服务器集群的资源管理方法和装置
CN108737270B (zh) * 2018-05-07 2021-01-26 北京京东尚科信息技术有限公司 一种服务器集群的资源管理方法和装置
JP2020027369A (ja) * 2018-08-09 2020-02-20 株式会社エヌケービー 広告配信システム、コンピュータの動作方法、及びクラウドサーバ
JP7206070B2 (ja) 2018-08-09 2023-01-17 株式会社エヌケービー 広告配信システム、コンピュータの動作方法、及びクラウドサーバ

Also Published As

Publication number Publication date
JP2019511788A (ja) 2019-04-25
US11165885B2 (en) 2021-11-02
EP3422672A4 (en) 2019-09-04
EP3422672B1 (en) 2020-09-02
CN107295033A (zh) 2017-10-24
CN107295033B (zh) 2020-07-28
US20190089812A1 (en) 2019-03-21
JP6687755B2 (ja) 2020-04-28
EP3422672A1 (en) 2019-01-02
ES2828900T3 (es) 2021-05-28

Similar Documents

Publication Publication Date Title
WO2017167130A1 (zh) 一种路由方法及装置
US10778792B1 (en) Providing user control of tracking user behavior
US10574771B2 (en) Methods and systems for rewriting scripts to redirect web requests
US11159630B2 (en) Third party validation of web content
US8825855B2 (en) Non-intrusive single sign-on mechanism in cloud services
JP5792198B2 (ja) ユーザの閲覧履歴に基づくｕｒｌフィルタリング
US9258249B2 (en) Resource access throttling
US11240257B2 (en) Domain name and URL visual verification for increased security
US20170359313A1 (en) Methods and Systems for Data Anonymization at a Proxy Server
US10158548B2 (en) Methods and systems for signing resource identifiers
US8028089B2 (en) On-deck detection for a web site
GB2500936A (en) Identifying the physical location of internet service providers using geo-location data provided by devices requesting data
CN108023867A (zh) 移动端网页广告过滤的方法、网关服务器及过滤服务器
US11436524B2 (en) Hosting machine learning models
US9686372B1 (en) Systems and methods for automatically rewriting network page code
Cobbe et al. What lies beneath: Transparency in online service supply chains
US11575761B2 (en) Method and system for propagating data between different domains in a privacy focused way
US11323537B1 (en) Generating early hints informational responses at an intermediary server
CN113888170A (zh) 地址溯源方法、装置及设备
US20180069898A1 (en) Methods and Systems for Managing Carrier Configurations in a Zero-Rated System
US8332469B1 (en) Web resource caching
US12028434B2 (en) Generating early hints informational responses at an intermediary server
CN108280100A (zh) 一种网页资源访问方法及装置

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2017773160

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2018551227

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017773160

Country of ref document: EP

Effective date: 20180927

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

Ref document number: 17773160

Country of ref document: EP

Kind code of ref document: A1