WO2021017970A1 - 一种调度访问请求的方法、装置、介质及设备 - Google Patents

一种调度访问请求的方法、装置、介质及设备 Download PDF

Info

Publication number
WO2021017970A1
WO2021017970A1 PCT/CN2020/103449 CN2020103449W WO2021017970A1 WO 2021017970 A1 WO2021017970 A1 WO 2021017970A1 CN 2020103449 W CN2020103449 W CN 2020103449W WO 2021017970 A1 WO2021017970 A1 WO 2021017970A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
cloud distribution
scheduling
module
mapping relationship
Prior art date
Application number
PCT/CN2020/103449
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 US17/630,349 priority Critical patent/US11706186B2/en
Publication of WO2021017970A1 publication Critical patent/WO2021017970A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/25—Mapping addresses of the same type
    • H04L61/2503—Translation of Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/101—Server selection for load balancing based on network conditions
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1021—Server selection for load balancing based on client or server locations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • This application relates to but is not limited to the field of communications technology, and in particular to a method, device, medium and equipment for scheduling access requests.
  • the content delivery network (Content Delivery Network, CDN) is based on the operator's Local Domain Name System (LDNS) to schedule user access requests, so that users can access cloud distribution nodes in the nearest region.
  • LDNS Local Domain Name System
  • this article provides a method, device, medium and equipment for scheduling access requests.
  • a method for scheduling access requests including:
  • mapping relationship is delivered to the scheduling agent module of the cloud distribution node in the network.
  • selecting at least one preferred node of the access source IP segment from cloud distribution nodes of the city operator includes:
  • selecting at least one preferred node of the access source IP segment from the cloud distribution nodes of the city operator further includes: obtaining the real-time load status of the cloud distribution node of the city operator;
  • the selecting the preferred node according to the historical network transmission status parameter includes: selecting the preferred node according to the historical network transmission status parameter and the real-time load condition.
  • the method further includes: after the cloud distribution node receives the user access request, the scheduling agent module of the cloud distribution node schedules the user access request according to the mapping relationship.
  • the scheduling agent module of the cloud distribution node scheduling the user access request according to the mapping relationship includes: determining the access source IP segment to which the source IP in the user access request belongs, and querying the user access request according to the mapping relationship According to the IP of the preferred node corresponding to the access source IP segment, determine whether the current cloud distribution node is the preferred node, if so, return an access response, if not, return the IP of the preferred node to indicate a redirection operation.
  • the method further includes: real-time detection of the cloud distribution node, and when it is detected that the cloud distribution node is in a fault state, modifying the mapping relationship, the mapping relationship includes a plurality of preferred nodes and includes the cloud distribution in the fault state When it is a node, delete the cloud distribution node in a fault state from the mapping relationship, and deliver the modified mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • an apparatus for scheduling access requests including:
  • the first determining module is configured to determine the city and city operator corresponding to each access source IP segment
  • the first selection module selects at least one preferred node in the access source IP segment from cloud distribution nodes of the city operator;
  • the second determining module determines the mapping relationship between the access source IP segment and the IP of the preferred node
  • the sending module is configured to deliver the mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • the first selection module includes a first acquisition module and a second selection module
  • the first obtaining module is configured to obtain historical network transmission state parameters when the cloud distribution node of the city operator processes the data of the access source IP segment;
  • the second selection module is configured to select a preferred node according to historical network transmission state parameters.
  • the first selection module further includes a second acquisition module
  • the second obtaining module is configured to obtain the real-time load status of the cloud distribution node of the city operator
  • the second selection module is also configured to select a preferred node based on historical network transmission status parameters and the real-time load situation.
  • it also includes a receiving module and a dispatching agent module at the cloud distribution node;
  • the receiving module is configured to receive a user access request
  • the scheduling proxy module is configured to schedule the user access request according to the mapping relationship.
  • the dispatch agent module includes:
  • the third determining module is configured to determine the access source IP segment to which the source IP in the user access request belongs;
  • a query module configured to query the IP of the preferred node corresponding to the access source IP segment according to the mapping relationship
  • a judging module configured to judge whether the current cloud distribution node is the preferred node
  • the feedback module is configured to return an access response when the current cloud distribution node is the preferred node, and when the current cloud distribution node is not the preferred node, return the IP of the preferred node to indicate a redirection operation.
  • the detection module is configured to perform real-time detection of cloud distribution nodes
  • the modification module is configured to modify the mapping relationship when the detection module detects that the cloud distribution node is in a fault state.
  • the mapping relationship includes multiple preferred nodes and includes a cloud distribution node in a fault state, The cloud distribution node in the failed state is deleted from the mapping relationship;
  • the sending module is also configured to deliver the modified mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method when the computer program is executed.
  • a computer device including a processor, a memory, and a computer program stored on the memory, and the processor implements the steps of the method when the computer program is executed by the processor.
  • Fig. 1 is a flow chart showing a method for scheduling access requests according to an exemplary embodiment.
  • Fig. 2 is a block diagram showing a system for scheduling access requests according to an exemplary embodiment
  • Fig. 3 is a block diagram showing a device for scheduling access requests according to an exemplary embodiment
  • Fig. 4 is a block diagram showing a computer device according to an exemplary embodiment.
  • Fig. 1 is a flow chart showing a method for scheduling access requests according to an exemplary embodiment. The method includes:
  • Step S11 Determine the city and city operator corresponding to each visit source IP segment
  • Step S12 selecting at least one preferred node in the access source IP segment from cloud distribution nodes of the city operator;
  • Step S13 Determine the mapping relationship between the access source IP segment and the IP of the preferred node
  • Step S14 Deliver the mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • This method allows users in the same province to use the same or different LDNS to achieve urban granular scheduling control by setting user IP segments based on city granularity, allowing users to schedule access to the best city-level service node according to city-level scheduling, saving scheduling paths, and improving scheduling efficiency. Avoid waste of scheduling resources.
  • the cloud distribution node is a CDN node.
  • step S11 log information is collected from the CDN log library to obtain and determine the city and city operator corresponding to each access source IP segment.
  • selecting at least one preferred node of the access source IP segment from the cloud distribution nodes of the city operator includes: obtaining the cloud distribution of the city operator by invoking an anti-PING interface
  • the historical network transmission state parameter when the node processes the data of the access source IP segment, and the preferred node is selected according to the historical network transmission state parameter.
  • Network transmission status parameters refer to data representing the status of network data transmission, such as delay time, packet loss rate, routing hops, etc.
  • selecting at least one preferred node of the access source IP segment from the cloud distribution nodes of the city operator in step S12 further includes: obtaining the real-time load status of the cloud distribution node of the city operator .
  • This real-time load situation includes at least one of the following information: bandwidth load, CPU load, disk load, and network card load.
  • selecting a preferred node based on historical network transmission state parameters further includes: selecting a preferred node based on historical network transmission state parameters and the real-time load situation.
  • the same user source IP segment corresponds to one preferred node, or the same user source IP segment corresponds to multiple preferred nodes, and all preferred nodes are sorted in order of priority from high to low.
  • the method further includes: real-time detection of the cloud distribution node, and when it is detected that the cloud distribution node is in a fault state, modifying the mapping relationship, the mapping relationship includes a plurality of preferred nodes and includes the failure state
  • the cloud distribution node in the faulty state is deleted from the mapping relationship, and the modified mapping relationship is delivered to the scheduling agent module of the cloud distribution node in the network.
  • This scheduling agent module is specifically a 302 scheduling agent module. Among them, the scheduling performed by the 302 scheduling agent module is effective in real time. Compared with the prior art scheduling method, it needs to wait for a DNSTTL effective time to take effect. The scheduling method of the 302 scheduling agent module can take effect immediately, effectively avoiding the delay in the effective time. Network scheduling errors greatly improve the immediacy and effectiveness of the network.
  • the method further includes step S15.
  • the scheduling agent module of the cloud distribution node schedules the user access request according to the mapping relationship. Specifically: Determine the access source IP segment to which the source IP in the user access request belongs, query the IP of the preferred node corresponding to the access source IP segment according to the mapping relationship, and determine whether the current cloud distribution node is the preferred node If yes, return an access response, if no, return the IP of the preferred node to indicate a redirection operation.
  • the scheduling access request system includes a quality center processor, a log library, a database, and a cloud distribution node.
  • the corresponding preferred node is the cloud distribution node of the first operator in the city of A-1 in province A, and the IP of this node is 3.3.3.3.
  • mapping relationship 192.168.1.0 ⁇ 24-->3.3.3.3 is formed and sent to the cloud distribution nodes of the entire network.
  • the cloud distribution node with IP 3.3.3.3 After the cloud distribution node with IP 3.3.3.3 receives the user access request, it determines that the source IP of the user access request is 192.168.1.1, the user source IP segment to which this IP belongs is 192.168.1.0-24, and determines the IP segment
  • the preferred node is a cloud distribution node whose IP is 3.3.3.3, and it is determined that the current cloud distribution node is the preferred node, and an access response is returned.
  • the cloud distribution node with IP 2.2.2.2 is the cloud distribution node of the first operator in the city of A-1 in province A. After receiving the user access request, it is determined that the source IP of the user access request is 192.168.1.1, and the IP belongs to The user source IP segment of is 192.168.1.0-24, determine the preferred node of this IP segment is the cloud distribution node with IP 3.3.3.3, determine that the current cloud distribution node is not this preferred node, and return the IP of the preferred node to indicate the redirection operation , To make the user re-initiate an access request to this preferred node.
  • Fig. 3 is a block diagram showing a device for scheduling access requests according to an exemplary embodiment.
  • the device includes:
  • the first determining module 301 is configured to determine the city and city operator corresponding to each access source IP segment;
  • the first selection module 302 selects at least one preferred node in the access source IP segment from cloud distribution nodes of the city operator;
  • the second determining module 303 determines the mapping relationship between the access source IP segment and the IP of the preferred node
  • the sending module 304 is configured to deliver the mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • the first selection module 302 includes a first acquisition module and a second selection module
  • the first obtaining module is configured to obtain historical network transmission state parameters when the cloud distribution node of the city operator processes the data of the access source IP segment;
  • the second selection module is configured to select a preferred node according to historical network transmission state parameters.
  • the first selection module 302 further includes a second acquisition module
  • the second obtaining module is configured to obtain the real-time load situation of the cloud distribution node of the city operator
  • the second selection module is also configured to select a preferred node based on historical network transmission status parameters and the real-time load situation.
  • the device further includes: a receiving module and a scheduling agent module located at the cloud distribution node;
  • the receiving module is configured to receive a user access request
  • the scheduling proxy module is configured to schedule the user access request according to the mapping relationship.
  • the dispatch agent module includes:
  • the third determining module is configured to determine the access source IP segment to which the source IP in the user access request belongs;
  • a query module configured to query the IP of the preferred node corresponding to the access source IP segment according to the mapping relationship
  • a judging module configured to judge whether the current cloud distribution node is the preferred node
  • the feedback module is configured to return an access response when the current cloud distribution node is the preferred node, and when the current cloud distribution node is not the preferred node, return the IP of the preferred node to indicate a redirection operation.
  • the device further includes:
  • the detection module is configured to perform real-time detection of cloud distribution nodes
  • the modification module is configured to modify the mapping relationship when the detection module detects that the cloud distribution node is in a fault state.
  • the mapping relationship includes multiple preferred nodes and includes a cloud distribution node in a fault state, The cloud distribution node in the failed state is deleted from the mapping relationship;
  • the sending module 104 is also configured to deliver the modified mapping relationship to the scheduling agent module of the cloud distribution node in the network.
  • Fig. 4 is a block diagram showing a computer device 400 for scheduling access requests according to an exemplary embodiment.
  • the computer device 400 may be provided as a server. 4
  • the computer device 400 includes a processor 401, and the number of processors can be set to one or more as required.
  • the computer device 400 also includes a memory 402 configured to store instructions executable by the processor 401, such as application programs. The number of memories can be set to one or more as required.
  • the stored application program can be one or more.
  • the processor 401 is configured to execute instructions to perform the above methods.
  • This document also provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed, the steps of the above method are realized.
  • the embodiments of the present application may be provided as methods, devices (equipment), or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media containing computer-usable program codes.
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storing information (such as computer readable instructions, data structures, program modules, or other data) , Including but not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or can be used for Any other medium that stores desired information and can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media .
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

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

Abstract

本文是关于一种调度访问请求的方法、装置、介质及设备，此方法包括：确定每个访问来源IP段对应的城市及城市运营商；从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；确定所述访问来源IP段与优选节点的IP的映射关系；将所述映射关系下发至网络中的云分发节点的调度代理模块。本文通过设置基于城市粒度的用户IP段，可以使同省用户使用相同或不同LDNS实现城市粒度调度控制，使用户按城市级别调度访问最佳城市级别的服务节点，节省调度路径，提高调度效率，避免调度资源浪费。

Description

一种调度访问请求的方法、装置、介质及设备
本申请要求在2019年07月31日提交中国专利局、申请号为201910699324.1，发明名称为“一种调度访问请求的方法、装置、介质及设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及但不限于通信技术领域，尤其涉及一种调度访问请求的方法、装置、介质及设备。
背景技术
内容分发网络(Content Delivery Network，CDN)中基于运营商的本地网域名称系统(Local Domain Name System，LDNS)来调度用户访问请求，使用户访问最近地域的云分发节点。在同一省份运营商中包含多个城市云分发节点，同一省份运营商存在共用LDNS的应用场景，并且现有的互联网用户使用LDNS时设置方式杂乱繁多，在调度过程中存在浪费调度资源的情况，并且还会影响大文件的正常下载。
发明内容
为克服相关技术中存在的问题，本文提供了一种调度访问请求的方法、装置、介质及设备。
根据本文的一方面，提供了一种调度访问请求的方法，包括：
确定每个访问来源IP段对应的城市及城市运营商；
从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
确定所述访问来源IP段与优选节点的IP的映射关系；
将所述映射关系下发至网络中的云分发节点的调度代理模块。
其中，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点包括：
获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数，根据历史网络传输状态参数选择优选节点。
其中，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点还包括：获取所述城市运营商的云分发节点的实时负载情况；
所述根据历史网络传输状态参数选择优选节点包括:根据历史网络传输状态参数和所述实时负载情况选择优选节点。
其中，所述方法还包括：在云分发节点接收到用户访问请求后，所述云分发节点的调度代理模块根据所述映射关系对所述用户访问请求进行调度。
其中，所述云分发节点的调度代理模块根据所述映射关系对所述用户访问请求进行调度包括：确定所述用户访问请求中的来源IP所属的访问来源IP段，根据所述映射关系查询所述访问来源IP段对应的优选节点的IP，判断当前云分发节点是否是所述优选节点，如果是，返回访问响应，如果否，返回所述优选节点的IP指示重定向操作。
其中，所述方法还包括：对云分发节点进行实时检测，检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除，将修改后的映射关系下发至网络中的云分发节点的调度代理模块。
根据本文的另一方面，提供了一种调度访问请求的装置，包括：
第一确定模块，被配置为确定每个访问来源IP段对应的城市及城市运营商；
第一选择模块，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
第二确定模块，确定所述访问来源IP段与优选节点的IP的映射关系；
发送模块，被配置为将所述映射关系下发至网络中的云分发节点的调度代理模块。
其中，所述第一选择模块包括第一获取模块和第二选择模块；
所述第一获取模块，被配置为获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数；
所述第二选择模块，被配置为根据历史网络传输状态参数选择优选节点。
其中，所述第一选择模块还包括第二获取模块；
所述第二获取模块，被配置为获取所述城市运营商的云分发节点的实时负载情况；
所述第二选择模块，还被配置为根据历史网络传输状态参数和所述实时负载情况选择优选节点。
其中，还包括位于云分发节点的接收模块和调度代理模块；
所述接收模块，被配置为接收到用户访问请求；
所述调度代理模块，被配置为根据所述映射关系对所述用户访问请求进行调度。
其中，所述调度代理模块包括：
第三确定模块，被配置为确定所述用户访问请求中的来源IP所属的访问来源IP段；
查询模块，被配置为根据所述映射关系查询所述访问来源IP段对应的优选节点的IP；
判断模块，被配置为判断当前云分发节点是否是所述优选节点；
反馈模块，被配置为在当前云分发节点是所述优选节点时，返回访问响应，在在当前云分发节点不是所述优选节点时，返回所述优选节点的IP指示重定向操作。
其中，还包括：
检测模块，被配置为对云分发节点进行实时检测；
修改模块，被配置为在所述检测模块检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除；
所述发送模块，还被配置为将修改后的映射关系下发至网络中的云分发节 点的调度代理模块。
根据本文的另一方面，提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被执行时实现所述方法的步骤。
根据本文的另一方面，提供了一种计算机设备，包括处理器、存储器和存储于所述存储器上的计算机程序，所述处理器执行所述计算机程序时实现所述方法的步骤。
本文通过设置基于城市粒度的用户IP段，可以使同省用户使用相同或不同LDNS实现城市粒度调度控制，使用户按城市级别调度访问最佳城市级别的服务节点，节省调度路径，提高调度效率，避免调度资源浪费。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本文。
附图说明
构成本申请的一部分的附图用来提供对本申请的进一步理解，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是根据一示例性实施例示出的一种调度访问请求的方法的流程图。
图2是根据一示例性实施例示出的一种调度访问请求的系统的框图；
图3是根据一示例性实施例示出的一种调度访问请求的装置的框图；
图4是根据一示例性实施例示出的一种计算机设备的框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
图1是根据一示例性实施例示出的一种调度访问请求的方法的流程图，此方法包括：
步骤S11，确定每个访问来源IP段对应的城市及城市运营商；
步骤S12，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
步骤S13，确定所述访问来源IP段与优选节点的IP的映射关系；
步骤S14，将所述映射关系下发至网络中的云分发节点的调度代理模块。
本方法通过设置基于城市粒度的用户IP段，可以使同省用户使用相同或不同LDNS实现城市粒度调度控制，使用户按城市级别调度访问最佳城市级别的服务节点，节省调度路径，提高调度效率，避免调度资源浪费。
在一种实施例中，云分发节点是CDN节点。
在一种实施例中，步骤S11中，通过从CDN日志库中采集日志信息，从而获取确定每个访问来源IP段对应的城市及城市运营商。
在一种实施例中，步骤S12中从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点包括：通过调用反PING接口，获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数，根据历史网络传输状态参数选择优选节点。网络传输状态参数是指表示网络数据传输状态的数据，例如延时时长、丢包率、路由跳数等。
在一种实施例中，步骤S12中从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点还包括：获取所述城市运营商的云分发节点的实时负载情况。此实时负载情况包括以下信息中的至少一种：带宽负载、CPU负载、磁盘负载、网卡负载。其中，根据历史网络传输状态参数选择优选节点还包括:根据历史网络传输状态参数和所述实时负载情况选择优选节点。
在一实施例中，在映射关系中，同一用户来源IP段对应于一个优选节点，或者，同一用户来源IP段对应于多个优选节点，所有优选节点按照优先级从高到低的顺序排序。将映射关系存储至数据库。
在一实施例中，本方法还包括：对云分发节点进行实时检测，检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节 点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除，将修改后的映射关系下发至网络中的云分发节点的调度代理模块。此调度代理模块具体为302调度代理模块。其中，302调度代理模块所执行的调度是实时生效的，相对比现有技术的调度方式需要等待一个DNSTTL生效时间才能生效，302调度代理模块的调度方式可以即时生效，有效避免生效时间延迟导致的网络调度错误，大大提高网络的即时性和有效性。
在一实施例中，本方法还包括步骤S15，在云分发节点接收到用户访问请求后，所述云分发节点的调度代理模块根据所述映射关系对所述用户访问请求进行调度。具体的：确定所述用户访问请求中的来源IP所属的访问来源IP段，根据所述映射关系查询所述访问来源IP段对应的优选节点的IP，判断当前云分发节点是否是所述优选节点，如果是，返回访问响应，如果否，返回所述优选节点的IP指示重定向操作。
如图2所示，调度访问请求系统包括质量中心处理器，日志库、数据库、云分发节点。
下面通过一具体实施例进行详细说明。
确定来源IP段192.168.1.0～24属于A省A-1城市，并且属于A省A-1城市的第一运营商。
对应的优选节点为A省A-1城市的第一运营商的云分发节点，此节点的IP为3.3.3.3。
构成此映射关系192.168.1.0～24-->3.3.3.3并发送至全网络的云分发节点。
IP为3.3.3.3的云分发节点接收到用户访问请求后，确定此用户访问请求的来源IP为192.168.1.1，确定此IP所属的用户来源IP段为192.168.1.0～24，确定此IP段的优选节点为的IP为3.3.3.3的云分发节点，判断当前云分发节点是此优选节点，返回访问响应。
IP为2.2.2.2的云分发节点是A省A-1城市的第一运营商的云分发节点，接收到用户访问请求后，确定此用户访问请求的来源IP为192.168.1.1，确定此IP所属的用户来源IP段为192.168.1.0～24，确定此IP段的优选节点为的IP为3.3.3.3的云分发节点，判断当前云分发节点不是此优选节点，返回优选节点的 IP指示重定向操作,使用户重新向此优选节点发起访问请求。
图3是根据一示例性实施例示出的一种调度访问请求的装置的框图，此装置包括：
第一确定模块301，被配置为确定每个访问来源IP段对应的城市及城市运营商；
第一选择模块302，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
第二确定模块303，确定所述访问来源IP段与优选节点的IP的映射关系；
发送模块304，被配置为将所述映射关系下发至网络中的云分发节点的调度代理模块。
在一实施例中，第一选择模块302包括第一获取模块和第二选择模块；
第一获取模块，被配置为获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数；
第二选择模块，被配置为根据历史网络传输状态参数选择优选节点。
在一实施例中，第一选择模块302还包括第二获取模块；
第二获取模块，被配置为获取所述城市运营商的云分发节点的实时负载情况；
第二选择模块，还被配置为根据历史网络传输状态参数和所述实时负载情况选择优选节点。
在一实施例中，本装置还包括：还包括位于云分发节点的接收模块和调度代理模块；
所述接收模块，被配置为接收到用户访问请求；
所述调度代理模块，被配置为根据所述映射关系对所述用户访问请求进行调度。
在一实施例中，调度代理模块包括：
第三确定模块，被配置为确定所述用户访问请求中的来源IP所属的访问来源IP段；
查询模块，被配置为根据所述映射关系查询所述访问来源IP段对应的优选节点的IP；
判断模块，被配置为判断当前云分发节点是否是所述优选节点；
反馈模块，被配置为在当前云分发节点是所述优选节点时，返回访问响应，在在当前云分发节点不是所述优选节点时，返回所述优选节点的IP指示重定向操作。
在一实施例中，本装置还包括：
检测模块，被配置为对云分发节点进行实时检测；
修改模块，被配置为在所述检测模块检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除；
所述发送模块104，还被配置为将修改后的映射关系下发至网络中的云分发节点的调度代理模块。
图4是根据一示例性实施例示出的一种用于调度访问请求的计算机设备400的框图。例如，计算机设备400可以被提供为一服务器。参照图4，计算机设备400包括处理器401，处理器的个数可以根据需要设置为一个或者多个。计算机设备400还包括存储器402，被配置为存储可由处理器401的执行的指令，例如应用程序。存储器的个数可以根据需要设置一个或者多个。其存储的应用程序可以为一个或者多个。处理器401被配置为执行指令，以执行上述方法。
本文还提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被执行时实现上述方法的步骤。
本领域技术人员应明白，本申请的实施例可提供为方法、装置(设备)、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质上实施的计算机程序产品的形式。计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质,包括但不限于RAM、ROM、EEPROM、闪存或其他存储 器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质等。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本申请是参照根据本发明实施例的方法、装置(设备)和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的物品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括……”限定的要素，并不排除在包括所述要素的物品或者设备中还存在另外的相同要素。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申 请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请的意图也包含这些改动和变型在内。
工业实用性
本文通过设置基于城市粒度的用户IP段，可以使同省用户使用相同或不同LDNS实现城市粒度调度控制，使用户按城市级别调度访问最佳城市级别的服务节点，节省调度路径，提高调度效率，避免调度资源浪费。

Claims (14)

  1. 一种调度访问请求的方法，包括：
    确定每个访问来源IP段对应的城市及城市运营商；
    从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
    确定所述访问来源IP段与优选节点的IP的映射关系；
    将所述映射关系下发至网络中的云分发节点的调度代理模块。
  2. 如权利要求1所述的调度访问请求的方法，其中，
    从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点包括：
    获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数，根据历史网络传输状态参数选择优选节点。
  3. 如权利要求2所述的调度访问请求的方法，其中，
    从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点还包括：获取所述城市运营商的云分发节点的实时负载情况；
    所述根据历史网络传输状态参数选择优选节点包括：根据历史网络传输状态参数和所述实时负载情况选择优选节点。
  4. 如权利要求1所述的调度访问请求的方法，所述方法还包括：
    在云分发节点接收到用户访问请求后，所述云分发节点的调度代理模块根据所述映射关系对所述用户访问请求进行调度。
  5. 如权利要求4所述的调度访问请求的方法，其中，
    所述云分发节点的调度代理模块根据所述映射关系对所述用户访问请求进行调度包括：确定所述用户访问请求中的来源IP所属的访问来源IP段，根据所述映射关系查询所述访问来源IP段对应的优选节点的IP，判断当前云分发节点是否是所述优选节点，如果是，返回访问响应，如果否，返回所述优选节点的IP指示重定向操作。
  6. 如权利要求1所述的调度访问请求的方法，所述方法还包括：
    对云分发节点进行实时检测，检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除，将修改后的映射关系下发至网络中的云分发节点的调度代理模块。
  7. 一种调度访问请求的装置，包括：
    第一确定模块，被配置为确定每个访问来源IP段对应的城市及城市运营商；
    第一选择模块，从所述城市运营商的云分发节点中选择所述访问来源IP段的至少一优选节点；
    第二确定模块，确定所述访问来源IP段与优选节点的IP的映射关系；
    发送模块，被配置为将所述映射关系下发至网络中的云分发节点的调度代理模块。
  8. 如权利要求7所述的调度访问请求的装置，其中，
    所述第一选择模块包括第一获取模块和第二选择模块；
    所述第一获取模块，被配置为获取所述城市运营商的云分发节点处理所述访问来源IP段的数据时的历史网络传输状态参数；
    所述第二选择模块，被配置为根据历史网络传输状态参数选择优选节点。
  9. 如权利要求8所述的调度访问请求的装置，其中，
    所述第一选择模块还包括第二获取模块；
    所述第二获取模块，被配置为获取所述城市运营商的云分发节点的实时负载情况；
    所述第二选择模块，还被配置为根据历史网络传输状态参数和所述实时负载情况选择优选节点。
  10. 如权利要求7所述的调度访问请求的装置，还包括位于云分发节点的接收模块和调度代理模块；
    所述接收模块，被配置为接收到用户访问请求；
    所述调度代理模块，被配置为根据所述映射关系对所述用户访问请求进行 调度。
  11. 如权利要求10所述的调度访问请求的装置，其中，
    所述调度代理模块包括：
    第三确定模块，被配置为确定所述用户访问请求中的来源IP所属的访问来源IP段；
    查询模块，被配置为根据所述映射关系查询所述访问来源IP段对应的优选节点的IP；
    判断模块，被配置为判断当前云分发节点是否是所述优选节点；
    反馈模块，被配置为在当前云分发节点是所述优选节点时，返回访问响应，在在当前云分发节点不是所述优选节点时，返回所述优选节点的IP指示重定向操作。
  12. 如权利要求7所述的调度访问请求的装置，还包括：
    检测模块，被配置为对云分发节点进行实时检测；
    修改模块，被配置为在所述检测模块检测到云分发节点处于故障状态时，修改所述映射关系，所述映射关系中包括多个优选节点并且包括处于故障状态的云分发节点时，将所述处于故障状态的云分发节点从所述映射关系中删除；
    所述发送模块，还被配置为将修改后的映射关系下发至网络中的云分发节点的调度代理模块。
  13. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被执行时实现如权利要求1～6中任意一项所述方法的步骤。
  14. 一种计算机设备，包括处理器、存储器和存储于所述存储器上的计算机程序，其中，述处理器执行所述计算机程序时实现如权利要求1～6中任意一项所述方法的步骤。
PCT/CN2020/103449 2019-07-31 2020-07-22 一种调度访问请求的方法、装置、介质及设备 WO2021017970A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/630,349 US11706186B2 (en) 2019-07-31 2020-07-22 Method, apparatus, medium, and device for scheduling access request

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910699324.1 2019-07-31
CN201910699324.1A CN112311829B (zh) 2019-07-31 2019-07-31 一种调度访问请求的方法、装置、介质及设备

Publications (1)

Publication Number Publication Date
WO2021017970A1 true WO2021017970A1 (zh) 2021-02-04

Family

ID=74229161

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/103449 WO2021017970A1 (zh) 2019-07-31 2020-07-22 一种调度访问请求的方法、装置、介质及设备

Country Status (3)

Country Link
US (1) US11706186B2 (zh)
CN (2) CN114172961A (zh)
WO (1) WO2021017970A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100125675A1 (en) * 2008-11-17 2010-05-20 Richardson David R Updating routing information based on client location
CN103825837A (zh) * 2014-02-19 2014-05-28 上海视云网络科技有限公司 一种节点负载的分布式cdn全局调度的方法
CN106211277A (zh) * 2016-06-29 2016-12-07 北京小米移动软件有限公司 智能选择服务器网络接入点的方法及装置
CN107071089A (zh) * 2017-05-18 2017-08-18 腾讯科技（深圳）有限公司 调度控制方法、装置和系统
CN109729186A (zh) * 2018-12-29 2019-05-07 北京金山云网络技术有限公司 一种配给策略确定方法及装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69925453T2 (de) * 1999-02-26 2006-05-11 Lucent Technologies Inc. Mobiles IP ohne Einkapselung
US6754699B2 (en) * 2000-07-19 2004-06-22 Speedera Networks, Inc. Content delivery and global traffic management network system
US7725602B2 (en) * 2000-07-19 2010-05-25 Akamai Technologies, Inc. Domain name resolution using a distributed DNS network
US8756341B1 (en) * 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
EP2355439A1 (en) * 2010-02-02 2011-08-10 Swisscom AG Accessing restricted services
US20140317313A1 (en) * 2011-08-29 2014-10-23 Hitachi, Ltd. Nat sub-topology management server
CN103825975B (zh) * 2014-02-26 2018-03-13 北京六间房科技有限公司 Cdn节点分配服务器及系统
CN104410691B (zh) 2014-11-27 2018-06-08 网宿科技股份有限公司 一种基于内容分发网络的网站加速方法及系统
US10097448B1 (en) * 2014-12-18 2018-10-09 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
US10033627B1 (en) * 2014-12-18 2018-07-24 Amazon Technologies, Inc. Routing mode and point-of-presence selection service
CN107645525A (zh) * 2016-07-21 2018-01-30 阿里巴巴集团控股有限公司 内容分发网络的探测处理、调度方法及相应装置、节点
WO2018095416A1 (zh) 2016-11-24 2018-05-31 腾讯科技（深圳）有限公司 信息处理方法、装置及系统
CN108616896B (zh) * 2016-12-06 2020-08-11 腾讯科技（深圳）有限公司 运营商识别方法、装置及互联网访问系统
CN106790530A (zh) * 2016-12-21 2017-05-31 北京云端智度科技有限公司 域名服务的跟踪和聚合方法
CN107395683B (zh) * 2017-06-26 2021-06-04 网宿科技股份有限公司 一种回源路径的选择方法及服务器
CN107277150A (zh) * 2017-06-28 2017-10-20 湖南科创信息技术股份有限公司 Cdn智能调度方法及系统
CN109639823A (zh) * 2018-12-28 2019-04-16 深圳市网心科技有限公司 网络节点调度方法及装置、计算机装置及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100125675A1 (en) * 2008-11-17 2010-05-20 Richardson David R Updating routing information based on client location
CN103825837A (zh) * 2014-02-19 2014-05-28 上海视云网络科技有限公司 一种节点负载的分布式cdn全局调度的方法
CN106211277A (zh) * 2016-06-29 2016-12-07 北京小米移动软件有限公司 智能选择服务器网络接入点的方法及装置
CN107071089A (zh) * 2017-05-18 2017-08-18 腾讯科技（深圳）有限公司 调度控制方法、装置和系统
CN109729186A (zh) * 2018-12-29 2019-05-07 北京金山云网络技术有限公司 一种配给策略确定方法及装置

Also Published As

Publication number Publication date
CN112311829A (zh) 2021-02-02
US20220294759A1 (en) 2022-09-15
US11706186B2 (en) 2023-07-18
CN112311829B (zh) 2022-05-17
CN114172961A (zh) 2022-03-11

Similar Documents

Publication Publication Date Title
US10404790B2 (en) HTTP scheduling system and method of content delivery network
US10715485B2 (en) Managing dynamic IP address assignments
CN106888270B (zh) 回源选路调度的方法和系统
US9503308B2 (en) Method, device and system for processing content
US20170366409A1 (en) Dynamic Acceleration in Content Delivery Network
KR20150054998A (ko) 클라우드 내에서 지리적으로 분산된 애플리케이션의 자동화 배치를 위한 방법 및 장치
CN105450780A (zh) 一种cdn系统及其回源方法
US20220094633A1 (en) Method and system for traffic scheduling
CN112532669B (zh) 一种网络边缘计算方法、装置及介质
US20160246517A1 (en) Methods for policy-based data tiering using a cloud architecture and devices thereof
CN109618003B (zh) 一种服务器规划方法、服务器及存储介质
CN108347479B (zh) 基于内容分发网络的多仓库静态资源上传方法和系统
CN113301079B (zh) 一种数据的获取方法、系统、计算设备及存储介质
CN109873855A (zh) 一种基于区块链网络的资源获取方法和系统
WO2021057369A1 (zh) HttpDNS调度方法、装置、介质及设备
US11606415B2 (en) Method, apparatus and system for processing an access request in a content delivery system
CN106789655B (zh) 一种路由通告报文的发送方法和装置
WO2021017970A1 (zh) 一种调度访问请求的方法、装置、介质及设备
CN112087382B (zh) 一种服务路由方法及装置
WO2023088362A1 (zh) 网络流量处理方法、装置、介质及电子设备
WO2022257791A1 (zh) 基于分布式网络的服务代码处理方法、装置、设备及介质
CN113612841B (zh) 任务调度方法、装置、计算机设备和存储介质
CN103685367A (zh) 离线下载系统和方法
CN112104566A (zh) 一种负载均衡的处理方法和装置
WO2022237670A1 (zh) 基于5g的边缘节点调度方法、装置、介质及设备

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: 20846064

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20846064

Country of ref document: EP

Kind code of ref document: A1