Private CDN (Content Delivery Network) scheduling device and method based on IP (Internet Protocol)

By deploying a private IP-based CDN scheduling device on the enterprise, using traffic accelerators and scheduling control centers to realize the scheduling of edge nodes, the problems of limited network bandwidth and complex DNS resolution within the enterprise are solved, and the content access efficiency and performance are improved, and the content access efficiency and performance are reduced. Operation and maintenance costs.

CN119094617APending Publication Date: 2024-12-06XIAMEN ANJIEYUN NETWORK CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411089268.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-09
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the prior art, the internal network architecture of enterprises is complex and the bandwidth is limited, resulting in network congestion and high access delays. The traditional CDN solution relies on DNS resolution is too complex and has high cost, making it difficult to achieve rapid scheduling.

Method used

Using IP-based privatized CDN scheduling devices, including traffic accelerators, scheduling control centers and edge cache nodes, the traffic accelerators and scheduling control centers are accelerated to realize the scheduling of edge nodes through the proxy of the user, and supports configuration according to IP segments or domain names to reduce the cost. Reform requirements of internal network topology.

Benefits of technology

It significantly improves the efficiency of user-side content access, reduces bandwidth consumption, improves application and service performance, reduces operation and maintenance costs, and simplifies the maintenance process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119094617A_ABST
    Figure CN119094617A_ABST
Patent Text Reader

Abstract

The invention discloses a private CDN scheduling device and method based on an IP, and relates to the technical field of network scheduling. The device comprises a traffic accelerator, a scheduling control center, a plurality of edge cache nodes and a source server matched with the edge cache nodes, the traffic accelerator is deployed on a PC or a server needing acceleration proxy of a private network, and the scheduling control center is used for configuring edge cache nodes and providing edge node information and scheduling strategy information for the traffic accelerator. The method aims at being compatible with user access modes of IP access and domain name access, the content access efficiency of the user side can be remarkably improved, bandwidth consumption is reduced, the application and service performance is improved, a large amount of energy is not needed to optimize and maintain, and the operation and maintenance cost is saved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of network scheduling, and in particular to a private CDN scheduling device and method based on IP. Background Art

[0002] Currently, many enterprises have complex internal network architectures and limited bandwidth, which can lead to network congestion and high access latency, seriously affecting the network environment and work efficiency. In order to optimize the internal network topology, upgrade hardware equipment, and optimize the configuration strategy of the intranet, it is too redundant and complex, and requires a lot of cost.

[0003] In the prior art, due to the technical complexity of the intranet cache architecture, it is usually necessary to modify the topology of the internal network to achieve load balancing control and content distribution; the cost is high, and it is necessary to update the server equipment and invest professionals to configure and maintain the entire cache architecture; and the traditional CDN solution is mainly based on DNS service to resolve the domain name, and then dispatch to the nearest cache node for data distribution. The process and maintenance of building a DNS resolution system in the intranet are too complicated, and it is necessary to set a domain name for each site. Moreover, due to the DNS diffusion mechanism, it cannot be dispatched quickly. Summary of the invention

[0004] In order to overcome the above problems or at least partially solve the above problems, the present invention provides an IP-based private CDN scheduling device and method, which is compatible with IP access and domain name access, can significantly improve user-side content access efficiency, reduce bandwidth consumption, and improve the performance of applications and services. It does not require a lot of effort to optimize and maintain, thus saving operation and maintenance costs.

[0005] In order to solve the above technical problems, the technical solution adopted by the present invention is:

[0006] In a first aspect, the present invention provides an IP-based privatized CDN scheduling device, including a traffic accelerator, a scheduling control center, multiple edge cache nodes, and a source server matching the edge cache nodes; the above-mentioned traffic accelerator is deployed on a PC or server in a private network that requires an accelerated proxy, and the above-mentioned scheduling control center is used to configure the edge cache nodes and provide edge node information and scheduling strategy information to the traffic accelerator.

[0007] This device includes a traffic accelerator, a scheduling control center, an edge cache node and a source server, wherein the edge cache node and the source server have the same functions as those in the public network CDN solution. Compared with the public network CDN, this device does not need to rely on DNS scheduling to implement the scheduling of edge nodes, and is mainly implemented through the user-side proxy acceleration traffic accelerator and the scheduling control center. The traffic accelerator is installed on the PC or server in the private network that needs to be accelerated, supports transparent proxy acceleration of all platform traffic, and communicates with the scheduling control center at the same time; the main functions of the scheduling control center include configuring all edge cache nodes, providing edge node information to the traffic accelerator, and supporting configuration by domain name or IP segment; in this device, the user side only needs to turn on the traffic accelerator, and no other configuration is required. When the browser accesses, the traffic will be obtained by the traffic accelerator, and according to the configuration of the scheduling control center, it will be allocated to different proxy channels, and then proxy the corresponding edge nodes.

[0008] The present invention deploys a cache architecture in the intranet and a proxy traffic accelerator on the user side, allowing users to obtain access to content cache nearby, which can significantly improve user-side content access efficiency, reduce bandwidth consumption, and improve the performance of applications and services. It does not require a lot of effort to optimize and maintain, saving operation and maintenance costs.

[0009] Based on the first aspect, further, the above-mentioned traffic accelerator obtains local access traffic through a hook mechanism, and proxies the local access traffic to the corresponding edge cache node according to the configuration information of the scheduling control center.

[0010] Based on the first aspect, further, the above-mentioned scheduling control center provides a configuration list based on IP scheduling, and the above-mentioned configuration list includes a correspondence between the acceleration service, the source server IP set of the acceleration service and the corresponding edge cache node.

[0011] Based on the first aspect, further, the above-mentioned traffic accelerator sets corresponding proxy nodes and cache nodes according to its own IP network segment and a configuration sheet based on IP scheduling.

[0012] Based on the first aspect, further, the scheduling control center configures all edge cache nodes according to the acceleration service domain name or IP segment.

[0013] In a second aspect, the present invention provides an IP-based private CDN scheduling method using the IP-based private CDN scheduling device as described above in the first aspect, comprising the following steps:

[0014] When the browser accesses, the access traffic is obtained based on the traffic accelerator;

[0015] According to the configuration information of the dispatch control center, the access traffic is distributed to different proxy nodes;

[0016] Depending on the different proxy nodes, the proxy is directed to the corresponding edge cache node.

[0017] This method is implemented based on the above-mentioned device. The user end only needs to turn on the traffic accelerator without any other configuration. When the browser accesses, the traffic will be obtained by the traffic accelerator and distributed to different proxy channels according to the configuration of the dispatching control center, and then proxy the corresponding edge nodes. The present invention deploys a cache architecture in the intranet and a proxy traffic accelerator on the user end, allowing users to obtain access to content cache nearby, which can significantly improve the user end content access efficiency, reduce bandwidth consumption, improve the performance of applications and services, and does not require a lot of effort to optimize and maintain, saving operation and maintenance costs.

[0018] Based on the second aspect, further, the above-mentioned obtaining access traffic based on the traffic accelerator includes the following steps:

[0019] The system-level hook component based on the traffic accelerator obtains access traffic and directs the obtained access traffic to the first-level proxy in the traffic accelerator.

[0020] Based on the second aspect, further, the method for allocating access traffic to different proxy nodes according to the configuration information of the scheduling control center includes the following steps:

[0021] According to the edge cache nodes corresponding to different IP segments in the configuration information, the IP or domain name that needs proxy acceleration, and the destination address of the traffic captured by the hook component based on the first-level proxy in the traffic accelerator;

[0022] According to the destination address, the access traffic is directed to the secondary proxy in the traffic accelerator. Based on the secondary proxy, it is determined whether the current access is http or https, and the judgment result is allocated to the corresponding proxy node.

[0023] Based on the second aspect, further, the method for determining whether the current access is http or https based on the secondary proxy and allocating to the corresponding proxy node based on the determination result includes the following steps:

[0024] Based on the secondary proxy, determine whether the current access is http or https;

[0025] If it is an https request, the secondary proxy first hooks and intercepts the https connect request;

[0026] Parse the destination address to select the corresponding proxy address, and establish an independent channel with the connect forward proxy. If the connection is successfully established, forward the request and return content to the traffic accelerator;

[0027] If it is an http request, it is sent directly to the corresponding reverse proxy;

[0028] If the forward proxy / reverse proxy connection fails, it will directly return to the source.

[0029] Based on the second aspect, further, the method for directing access traffic to a secondary proxy in a traffic accelerator according to a destination address includes the following steps:

[0030] Determine whether the destination address is an IP or domain name that requires proxy acceleration. If so, direct the access traffic to the secondary proxy in the traffic accelerator; if not, return directly to the source.

[0031] The present invention has at least the following advantages or beneficial effects:

[0032] 1. Simple framework: By installing the traffic accelerator and dispatch control center provided by this device on the user side, IP can be used directly for dispatching, and caching and content distribution can be achieved without spending a lot of money to transform the internal network topology. At the same time, the device will not affect the original network architecture of the intranet.

[0033] 2. High operation and maintenance efficiency: The dispatch control center provides configuration and monitoring. It only needs to configure the site IP of proxy acceleration and maintain edge cache information, without the need for multiple platforms for operation and maintenance;

[0034] 3. Low cost: Only edge cache nodes need to be provided, and no extensive modifications are required to the user end and internal network;

[0035] 4. Improve security: support configuration according to different network segments and control content access for different users;

[0036] 5. Improve convenience: The traffic accelerator does not require manual configuration operations, the user is unaware, and supports user-side proxy acceleration on all platforms. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0038] Figure 1 This is a structural diagram of a private CDN scheduling device based on IP according to an embodiment of the present invention;

[0039] Figure 2 This is a flow accelerator workflow diagram in an embodiment of the present invention;

[0040] Figure 3 This is a flow chart of the traffic accelerator proxy https in an embodiment of the present invention;

[0041] Figure 4 This is a schematic diagram of the configuration structure of the dispatching control center in an embodiment of the present invention;

[0042] Figure 5 Schematic diagram of the scheduling management page in an embodiment of the present invention. DETAILED DESCRIPTION

[0043] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

[0044] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0045] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

[0046] In the description of the embodiments of the present invention, "plurality" means at least 2.

[0047] In the description of the embodiments of the present invention, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "set", "install", "connect", and "connect" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal connection of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0048] Example:

[0049] Professional term explanation: CDN is based on the existing network, through a network of multiple interconnected servers, relying on edge servers deployed in various places, and through the load balancing, content distribution, scheduling and other functional modules of the central platform, so that users can obtain the required content nearby, reduce network congestion, and improve user access response speed and hit rate.

[0050] like Figure 1As shown, in the first aspect, an embodiment of the present invention provides an IP-based privatized CDN scheduling device, including a traffic accelerator, a scheduling control center, multiple edge cache nodes, and a source server matching the edge cache node; the above-mentioned traffic accelerator is deployed on a PC or server in a private network that needs to accelerate the proxy, and the above-mentioned scheduling control center is used to configure the edge cache node and provide the edge node information and scheduling policy information to the traffic accelerator. The scheduling control center is used to configure which customer IP segments need to be accelerated by which edge nodes. The scheduling control center includes a web management terminal and an openAPI gateway. The administrator configures the customer IP segment and the corresponding edge acceleration server IP on the web management terminal; the traffic accelerator installed on the user's PC will call the openAPI interface to obtain these scheduling information. The configuration information on the scheduling control center will change, and the traffic accelerator software installed on the PC will call the openAPI interface of the scheduling control center to query the scheduling policy in real time.

[0051] The above-mentioned dispatch control center provides a configuration list based on IP dispatch, which includes the corresponding relationship between the acceleration service, the source server IP set of the acceleration service and the corresponding edge cache node, such as Figure 4 shown.

[0052] The above-mentioned traffic accelerator sets corresponding proxy nodes and cache nodes according to its own IP network segment and the configuration sheet based on IP scheduling.

[0053] The above-mentioned dispatching and control center configures all edge cache nodes according to the domain name or IP segment of the acceleration business. The dispatching and control center configures all edge cache nodes according to the cache rules, source station configuration, HTTPS configuration, header control, access control and other comprehensive characteristics of the domain name or IP segment of the acceleration business, and forms a configuration rule base based on the configuration results of multiple configurations. Based on the rule base, dynamic adjustment and configuration are realized according to different business needs. The information configured by the dispatching and control center is dynamically changing. For example, the rules will be dynamically adjusted with the development of the business, and the headers will change dynamically according to business needs.

[0054] In the present invention, the dynamic configuration of the rule base solves the problem of dynamically determining the service edge node of a certain client according to the status of the business and edge node. The rule base is a process of dynamically establishing and adjusting according to demand, business characteristics, etc. For example, regional characteristics: the client IP of XX province is 192.168.11.0 / 24 or 192.168.2.0 / 24, and the allocated edge node IP is 192.168.11.91, then the service IP address of the corresponding IP segment needs to be configured; business requirements: when the client visits baidu.com, google. com and youtube.com, the traffic is accelerated, and when the client visits other websites, the traffic acceleration is not required, then the domain name or IP business corresponding to the traffic acceleration needs to be added to the business management for management; state characteristics: when the XX node fails or is unavailable, the backup service node IP selection needs to be designed in the scheduling management, and when the main service node is unavailable, it can automatically switch to the backup service node for service.

[0055] This device includes a traffic accelerator, a scheduling control center, an edge cache node and a source server, wherein the edge cache node and the source server have the same functions as those in the public network CDN solution. Compared with the public network CDN, this device does not need to rely on DNS scheduling to implement the scheduling of edge nodes, and is mainly implemented through the user-side proxy acceleration traffic accelerator and the scheduling control center. The traffic accelerator is installed on the PC or server in the private network that needs to be accelerated, supports transparent proxy acceleration of all platform traffic, and communicates with the scheduling control center at the same time; the main functions of the scheduling control center include configuring all edge cache nodes, providing edge node information to the traffic accelerator, and supporting configuration by domain name or IP segment; in this device, the user side only needs to turn on the traffic accelerator, and no other configuration is required. When the browser accesses, the traffic will be obtained by the traffic accelerator, and according to the configuration of the scheduling control center, it will be allocated to different proxy channels, and then proxy the corresponding edge nodes.

[0056] The present invention deploys a cache architecture in the intranet and deploys a proxy traffic accelerator on the user side, so that users can obtain access to content cache nearby, which can significantly improve the user-side content access efficiency, reduce bandwidth consumption, improve the performance of applications and services, and do not require a lot of effort to optimize and maintain, saving operation and maintenance costs. The cache architecture deployed in the intranet mainly includes the traffic accelerator software installed on the intranet user PC, the intranet edge cache node and the scheduling control center, as follows:

[0057] 1. The traffic accelerator software installed on the user's PC will hijack the user's traffic and obtain resources from the edge node if the user accesses certain intranet IP or domain name resources;

[0058] 2. Intranet edge cache nodes will be deployed in multiple computer rooms, each of which will have multiple cache machines deployed. User requests will be dispatched to a machine in computer room A based on the policy of the dispatch control center. If the request is dispatched to computer room A, it will be dispatched to a machine in computer room A based on the load balancing policy. If the cache does not hit, it will return to the source.

[0059] 3. The dispatching control center is also deployed in a computer room in the intranet. The networks of the dispatching control center computer room and the edge cache computer room are interconnected; the dispatching strategy is configured on the dispatching control center.

[0060] Based on the first aspect, further, the above-mentioned traffic accelerator obtains local access traffic through a hook mechanism, and proxies the local access traffic to the corresponding edge cache node according to the configuration information of the scheduling control center.

[0061] In some embodiments of the present invention, the traffic accelerator obtains local access traffic through a hook mechanism, and then proxies it to the corresponding edge cache node according to the scheduling configuration, such as Figure 2 As shown, the specific process is as follows:

[0062] 1. The traffic generated by the user end is captured by the system-level hook component of the traffic accelerator. The hook component here can adapt to the network traffic acquisition methods of different operating systems. The acquired traffic is directed to the first-level proxy in the traffic accelerator;

[0063] 2. The configuration obtained by the traffic accelerator from the dispatch control center includes the edge cache nodes corresponding to different IP segments, the IP or domain name that needs proxy acceleration, and the first-level proxy resolves the destination address of the hook traffic, and then directs it to the second-level proxy according to the corresponding destination address.

[0064] 3. The secondary proxy determines whether the current request is http or https, and forwards it to different addresses. Compared with the http proxy, the https proxy has a private certificate deployed in the intranet, which eliminates the need to deploy private certificates for each site in the traffic accelerator.

[0065] 4. The proxy server then requests the edge node, obtains the resource and returns it. If the node has no cache or it is expired, it will return the request to the source.

[0066] In a second aspect, an embodiment of the present invention provides an IP-based private CDN scheduling method using the IP-based private CDN scheduling device as described in the first aspect, comprising the following steps:

[0067] S1. When the browser accesses, the access traffic is obtained based on the traffic accelerator;

[0068] Furthermore, it includes: obtaining access traffic based on a system-level hook component of the traffic accelerator, and directing the obtained access traffic to a first-level proxy in the traffic accelerator.

[0069] S2, distributes access traffic to different proxy nodes according to the configuration information of the dispatch control center;

[0070] Furthermore, it includes: according to the edge cache nodes corresponding to different IP segments in the configuration information, the IP or domain name that needs proxy acceleration, and the destination address of the traffic captured by the hook component based on the first-level proxy in the traffic accelerator; directing the access traffic to the second-level proxy in the traffic accelerator according to the destination address, judging whether the current access is http or https based on the second-level proxy, and allocating it to the corresponding proxy node based on the judgment result.

[0071] Furthermore, the method for determining whether the current access is http or https based on the secondary proxy and allocating to the corresponding proxy node based on the determination result includes the following steps:

[0072] Based on the secondary proxy, determine whether the current access is http or https; if it is an https request, the secondary proxy first hooks and intercepts the https connect request; parses the destination address to select the corresponding proxy address, and establishes an independent channel with the connect forward proxy. If the connection is successfully established, forward the request and return content to the traffic accelerator; if it is an http request, send it directly to the corresponding reverse proxy; if the forward proxy / reverse proxy fails to establish a connection, it returns directly to the source.

[0073] Furthermore, the method for directing access traffic to a secondary proxy in a traffic accelerator according to a destination address includes the following steps:

[0074] Determine whether the destination address is an IP or domain name that requires proxy acceleration. If so, direct the access traffic to the secondary proxy in the traffic accelerator; if not, return directly to the source.

[0075] In some embodiments of the present invention, the secondary proxy supports direct proxying of https sites in the intranet, and solves the https request proxy problem through the secondary proxy of the traffic accelerator, such as Figure 3 As shown, the specific process is as follows:

[0076] Currently, if it is an https request, the secondary proxy first hooks and intercepts the https connect request;

[0077] Parse the destination address, select the corresponding proxy address, and establish an independent channel with the connect forward proxy. If the connection is successfully established, it will be returned to the traffic accelerator;

[0078] After the channel is established, forward the request and return the content;

[0079] If it is an http request, it is sent directly to the corresponding reverse proxy;

[0080] If the connection with the proxy fails, it will directly return to the source to prevent user access from being affected.

[0081] On the web management page of the dispatch control center, the administrator can configure the destination IP address or domain name, which dispatch policy information to adopt, and determine whether the corresponding destination address is the IP or domain name that needs proxy acceleration based on the dispatch policy information. The above dispatch policy information includes device status, service IP segment, backup service address, etc. The management page is as follows Figure 5 shown.

[0082] In some embodiments of the present invention, in addition to manually configuring scheduling policies, an automatic scheduling mechanism is also provided, in which the machine has its own scheduling policy, for example, automatically deciding whether to schedule traffic to a node based on the node status such as the node network quality and availability detected by the monitoring system.

[0083] And a correction mechanism is also provided in the present invention to ensure normal user access. If there is no correction mechanism for configuration errors, an error will be reported if the user accesses incorrectly. For example, the edge cache machine IP required to access the google.com domain name is 192.168.1.1, but the edge cache machine and google.com do not communicate at all, so when the user accesses google.com on the PC, an error will be reported, prompting modification. In the present invention, only configuration format errors will be automatically corrected. As long as the configuration format is correct, it will be considered correct. It will not be automatically corrected, but prompted by an error report. The backend needs to ensure that the configuration is visible and consistent with the background effective configuration. The following is a complete JSON format scheduling policy information:

[0084] {

[0085] "code":"000000",

[0086] "msg":"ok",

[0087] "data":{

[0088] "servers":[

[0089] {

[0090] "server":"192.168.11.91:33080",

[0091] "sslServer":"192.168.11.91:33080",

[0092] "ip":["192.168.11.0 / 24","192.168.2.0 / 24"]

[0093] }

[0094] ],

[0095] "domains":["google.com","youtube.com","baidu.com"],

[0096] "httpDomains":["baidu.com"],

[0097] "httpsDomains":["google.com","youtube.com"]

[0098] }

[0099] }

[0100] S3. According to different proxy nodes, the proxy is sent to the corresponding edge cache node.

[0101] This method is implemented based on the above-mentioned device. The user end only needs to turn on the traffic accelerator without any other configuration. When the browser accesses, the traffic will be obtained by the traffic accelerator and distributed to different proxy channels according to the configuration of the dispatching control center, and then proxy the corresponding edge nodes. The present invention deploys a cache architecture in the intranet and a proxy traffic accelerator on the user end, allowing users to obtain access to content cache nearby, which can significantly improve the user end content access efficiency, reduce bandwidth consumption, improve the performance of applications and services, and does not require a lot of effort to optimize and maintain, saving operation and maintenance costs.

[0102] In the embodiments provided in the present application, it should be understood that the disclosed method and system can also be implemented in other ways. The method and system embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the method and system, method and computer program product according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or the flowchart, and the combination of boxes in the block diagram and / or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0103] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

[0104] It will be apparent to those skilled in the art that the present application is not limited to the details of the exemplary embodiments described above, and that the present application can be implemented in other specific forms without departing from the spirit or essential features of the present application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims be included in the present application. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

Claims

1. A private CDN scheduling device based on IP, It is characterized in that It includes a traffic accelerator, a scheduling control center, multiple edge cache nodes and source servers matching the edge cache nodes; the traffic accelerator is deployed on a PC or server in a private network that needs an accelerated proxy, and the scheduling control center is used to configure the edge cache nodes and provide the traffic accelerator with edge node information and scheduling strategy information.

2. According to claim 1, a private CDN scheduling device based on IP, It is characterized in that The traffic accelerator obtains local access traffic through a hook mechanism, and proxies the local access traffic to the corresponding edge cache node according to the configuration information of the scheduling control center.

3. The IP-based private CDN scheduling device according to claim 1, It is characterized in that The scheduling control center provides a configuration list based on IP scheduling, and the configuration list includes the corresponding relationship between the acceleration service, the source server IP set of the acceleration service and the corresponding edge cache node.

4. The IP-based private CDN scheduling device according to claim 3, It is characterized in that The traffic accelerator sets corresponding proxy nodes and cache nodes according to its own IP network segment and a configuration sheet based on IP scheduling.

5. The IP-based private CDN scheduling device according to claim 1, It is characterized in that The dispatch control center configures all edge cache nodes according to the acceleration service domain name or IP segment.

6. A private CDN scheduling method based on IP using the private CDN scheduling device based on IP as claimed in any one of claims 1 to 5, It is characterized in that The following steps are involved: When the browser accesses, the access traffic is obtained based on the traffic accelerator; According to the configuration information of the dispatch control center, the access traffic is distributed to different proxy nodes; Depending on the different proxy nodes, the proxy is directed to the corresponding edge cache node.

7. The IP-based private CDN scheduling method according to claim 6, It is characterized in that The method of obtaining access traffic based on the traffic accelerator includes the following steps: The system-level hook component based on the traffic accelerator obtains access traffic and directs the obtained access traffic to the first-level proxy in the traffic accelerator.

8. According to claim 7, a private CDN scheduling method based on IP, It is characterized in that The method for distributing access traffic to different proxy nodes according to the configuration information of the dispatching control center comprises the following steps: According to the edge cache nodes corresponding to different IP segments in the configuration information, the IP or domain name that needs proxy acceleration, and the destination address of the traffic captured by the hook component based on the first-level proxy in the traffic accelerator; According to the destination address, the access traffic is directed to the secondary proxy in the traffic accelerator. Based on the secondary proxy, it is determined whether the current access is http or https, and the judgment result is allocated to the corresponding proxy node.

9. The IP-based private CDN scheduling method according to claim 8, It is characterized in that The method of determining whether the current access is http or https based on the secondary proxy and assigning it to the corresponding proxy node based on the determination result comprises the following steps: Based on the secondary proxy, determine whether the current access is http or https; If it is an https request, the secondary proxy first hooks and intercepts the https connect request; Parse the destination address to select the corresponding proxy address, and establish an independent channel with the connect forward proxy. If the connection is successfully established, forward the request and return content to the traffic accelerator; If it is an http request, it is sent directly to the corresponding reverse proxy; If the forward proxy / reverse proxy connection fails, it will directly return to the source.

10. The IP-based private CDN scheduling method according to claim 8, It is characterized in that The method for directing access traffic to a secondary proxy in a traffic accelerator according to a destination address comprises the following steps: Determine whether the destination address is an IP or domain name that requires proxy acceleration. If so, direct the access traffic to the secondary proxy in the traffic accelerator; if not, return directly to the source.