CN114338686A - Source returning method and device of CDN node server - Google Patents
Source returning method and device of CDN node server Download PDFInfo
- Publication number
- CN114338686A CN114338686A CN202111569130.3A CN202111569130A CN114338686A CN 114338686 A CN114338686 A CN 114338686A CN 202111569130 A CN202111569130 A CN 202111569130A CN 114338686 A CN114338686 A CN 114338686A
- Authority
- CN
- China
- Prior art keywords
- data
- request
- cdn node
- node server
- user side
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
-
- 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
-
- 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a back-to-source method of a CDN node server, which comprises the following steps: acquiring a data request of a user side according to the connection relation between a secondary CDN node server and the user side, searching corresponding request data according to the data request, and sending the corresponding request data to the user side; if the data request is not responded, the secondary CDN node server sends the data request to a primary CDN node server to search the request data and send the request data to a user side; and if the data request is not responded, the primary CDN node server sends the data request to an origin server to search the request data and send the request data to a user side. The request data are provided through the multi-stage CDN node servers, so that the times of data being sent back to the source node server are greatly reduced, the load of the source node server is reduced, and the stability of data acquisition is improved. The application also provides a source returning device of the CDN node server.
Description
Technical Field
The present application relates to a data access method, and in particular, to a method for returning a source to a CDN node server. The application also relates to a back-source method and a back-source device of the CDN node server.
Background
The basic idea of the CDN (content delivery network) is to avoid bottlenecks and links on the internet that may affect the data transmission speed and stability as much as possible, so that content transmission is faster and more stable. The main setting mode is that a layer of intelligent virtual network on the basis of the existing internet is formed by placing node servers at each position of the network, and the CDN system can redirect the request of a user to a service node closest to the user in real time according to network flow, connection of each node, load condition, distance to the user, response time and other comprehensive information. The method aims to enable the user to obtain the required content nearby, solve the problem of congestion of the Internet network and improve the response speed of the user for accessing the website.
In the prior art, a conventional CDN back-source policy is that when a user accesses a certain URL, if the content of the cache response is not cached in the resolved CDN node, or the cache expires, the CDN back-source node returns to the source station to obtain the content, and this back-source manner causes a load pressure of the source station to be large, so that stability and speed of data acquisition are affected.
Disclosure of Invention
In order to solve the problem of overlarge load of a source station caused by a conventional source returning mode, the application provides a source returning method of a CDN node server. The application also relates to a back-source method and a back-source device of the CDN node server.
The application provides a back-to-source method of a CDN node server, which comprises the following steps:
acquiring a data request of a user side according to the connection relation between a secondary CDN node server and the user side, searching corresponding request data according to the data request, and sending the corresponding request data to the user side;
if the data request is not responded, the secondary CDN node server sends the data request to a primary CDN node server to search the request data and send the request data to a user side;
and if the data request is not responded, the primary CDN node server sends the data request to an origin server to search the request data and send the request data to a user side.
Optionally, before the data request is sent to the source server, the method further includes:
and the primary node server sends the data request to an adjacent primary CDN node server to search for the requested data and send the requested data to a user side.
Optionally, the obtaining a data request of the user side according to the connection relationship between the secondary CDN node server and the user side includes:
the method comprises the steps of obtaining position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and a user side according to the position information, and determining the secondary CDN node servers according to the distance information.
Optionally, the data request being not responded includes: data not stored, data failed, or data error.
Optionally, the secondary CDN node server and the primary CDN node server record load information in real time, and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
The present application further provides a back-source device of the CDN node server, including:
the source returning module is used for acquiring a data request of the user side according to the connection relation between the secondary CDN node server and the user side, searching corresponding request data according to the data request and sending the corresponding request data to the user side;
the second-level CDN node server is used for searching the request data and sending the request data to a user side;
and the second forwarding module is used for sending the data request to an origin server by the primary CDN node server to search the request data and send the request data to a user side if the data request is not responded.
Optionally, the second forwarding module further includes:
and the parallel forwarding unit is used for sending the data request to an adjacent primary CDN node server by the primary node server to search the request data and send the request data to a user side.
Optionally, the method further includes:
the position query module is used for acquiring position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and the user side according to the position information, and determining the secondary CDN node servers according to the distance information.
Optionally, the data request being not responded includes: data not stored, data failed, or data error.
Optionally, the secondary CDN node server and the primary CDN node server record load information in real time, and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
The application has the advantages relative to the prior art:
the application provides a back-to-source method of a CDN node server, which comprises the following steps: acquiring a data request of a user side according to the connection relation between a secondary CDN node server and the user side, searching corresponding request data according to the data request, and sending the corresponding request data to the user side; if the data request is not responded, the secondary CDN node server sends the data request to a primary CDN node server to search the request data and send the request data to a user side; and if the data request is not responded, the primary CDN node server sends the data request to an origin server to search the request data and send the request data to a user side. The request data are provided through the multi-stage CDN node servers, so that the times of data being sent back to the source node server are greatly reduced, the load of the source node server is reduced, and the stability of data acquisition is improved.
Drawings
Fig. 1 is a flow chart of the back source of the CDN node server in the present application.
Fig. 2 is a schematic diagram of parallel requests of CDN node server data in the present application.
Fig. 3 is a schematic diagram of a back-source device of a CDN node server according to the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The application provides a back-to-source method of a CDN node server, which comprises the following steps: acquiring a data request of a user side according to the connection relation between a secondary CDN node server and the user side, searching corresponding request data according to the data request, and sending the corresponding request data to the user side; if the data request is not responded, the secondary CDN node server sends the data request to a primary CDN node server to search the request data and send the request data to a user side; and if the data request is not responded, the primary CDN node server sends the data request to an origin server to search the request data and send the request data to a user side. The request data are provided through the multi-stage CDN node servers, so that the times of data being sent back to the source node server are greatly reduced, the load of the source node server is reduced, and the stability of data acquisition is improved.
Fig. 1 is a flow chart of the back source of the CDN node server in the present application.
Referring to fig. 1, in S101, a data request of a user side is obtained according to a connection relationship between a secondary CDN node server and the user side, and corresponding request data is searched for according to the data request and sent to the user side.
In the present application, the CDN node servers are distributed in multiple stages, and include an origin server, where the origin server is a general server, and original storage of data is performed in the origin server. The source server is connected with a plurality of primary CDN servers, and the primary servers are distributed in each large area. For example, the large area may be a country or a province. The first-level CDN node servers are also mutually connected and can carry out communication and data transmission.
Each primary CDN server is connected with a plurality of secondary CDN servers, and the secondary CDN servers acquire request data from the source server through the primary CDN servers and send the request data to each client.
In the application, each CDN server including the primary CDN server and the secondary CDN server is connected through a communication cable to perform data transfer. Specifically, each CDN server is a node, and includes a CDN Cache device, and then each node constitutes a CDN node system, and each node is managed by an SLB (load balancing) device. The CDN Cache equipment is main function equipment in the node.
In the application, the user side is connected with and communicates with the secondary CDN node server, and specifically, the secondary CDN node server is a node with an optimal distance and is used for reducing transmission time of request data and reducing user waiting time. Preferably, the method comprises the steps of obtaining position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and the user side according to the position information, and determining the secondary CDN node servers according to the distance information.
Another embodiment is that the optimal secondary CDN node server of the back source is determined according to the following formula:
P＝R*T*Tio*C*F/S
wherein S is a geographical distance, R is a disk space available for the CDN server, T is an output bandwidth, Tio is an I/O bandwidth of a disk, C is a processing capacity of a CPU, and F is an idle resource of the CDN node. The larger the P, the larger the selection weight.
And the secondary CDN node server acquires a data request of the user side according to the connection relation between the secondary CDN node server and the user side, searches corresponding request data according to the data request and sends the corresponding request data to the user side.
Generally, if a user has requested the requested data, the secondary CDN node server may increase the requested data according to the data request. And the second-level CDN node server inquires and searches the request data from the cache, and when the request data is searched, the request data is sent to a user side for display.
Referring to fig. 1, if the data request is not responded, in S102, the secondary CDN node server sends the data request to a primary CDN node server to search for the requested data and send the requested data to the user side.
In this application, if the request data is not applied by the user side, the data will not exist in the secondary CDN server, or the request data is invalid due to too long time, the request data cannot be provided to the user side, and at this time, the secondary CDN node server will not be able to respond to the data request of the user side. Specifically, the data request non-response includes: data not stored, data failed, or data error. The user side refers to any user side connected with the same secondary CDN server.
In a specific operation, the secondary node server sets a preset search time length, and when the preset search time length is exceeded and the data request is not responded, the secondary node server is judged to not respond.
And then, the secondary CDN server sends the data request to a primary CDN server with a direct connection relation with the secondary CDN server, the primary CDN server searches the request data, and sends the request data to a user side.
Fig. 2 is a schematic diagram of parallel requests of CDN node server data in the present application.
Referring to fig. 2, in S201, when the primary CDN node server does not respond to the data request, the data request is sent to an adjacent primary CDN server.
If the primary CDN server does not respond, the primary CDN node server is judged to be incapable of providing the request data, so that the search can be continuously carried out from the primary node server adjacent to the primary CDN node server.
Referring to fig. 2, the adjacent one-level CDN server sends the data request to an origin server.
Referring to fig. 1, in S103, if the data request is not responded, the primary CDN node server sends the data request to an origin server to search for the requested data, and sends the requested data to a user side.
When the first-level CDN node server or an adjacent first-level CDN node server does not respond to the data request, it is determined that the first-level CDN node server or an adjacent first-level CDN node server does not cache the request data and therefore needs to obtain the request data from an origin server, so that the data request is sent to the origin server to search for the request data, and the request data is sent to a user side.
At this time, the primary CDN node server and the secondary CDN node server cache the request data. When the requested data is requested again, it can be obtained from the secondary or primary CDN node server. Preferably, the secondary CDN node server and the primary CDN node server further record load information in real time, and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
After the secondary CDN node server obtains the request data, the type of user side equipment is judged according to the data request of the user, and the data is processed according to the type of the equipment and then sent to the user side for displaying.
Preferably, the secondary CDN node server further includes a history data storage device, and the history data storage device stores a history data and device type and history data correspondence table. After the secondary CDN node server obtains the data request, firstly judging the user terminal device type contained in the data request, searching whether the historical data has the request data corresponding to the user terminal device type requested by the user terminal from the device type and historical data corresponding table according to the device type, if not, returning the source, and if so, sending the historical data to the user terminal.
The present application further provides a back-source device of the CDN node server, including: back to source module 301, first forwarding module 302 and second forwarding module 303.
Fig. 3 is a schematic diagram of a back-source device of a CDN node server according to the present application.
Referring to fig. 3, the source returning module 301 is configured to obtain a data request of a user side according to a connection relationship between a secondary CDN node server and the user side, search for corresponding request data according to the data request, and send the request data to the user side.
In the present application, the CDN node servers are distributed in multiple stages, and include an origin server, where the origin server is a general server, and original storage of data is performed in the origin server. The source server is connected with a plurality of primary CDN servers, and the primary servers are distributed in each large area. For example, the large area may be a country or a province. The first-level CDN node servers are also mutually connected and can carry out communication and data transmission.
Each primary CDN server is connected with a plurality of secondary CDN servers, and the secondary CDN servers acquire request data from the source server through the primary CDN servers and send the request data to each client.
In the application, each CDN server including the primary CDN server and the secondary CDN server is connected through a communication cable to perform data transfer. Specifically, each CDN server is a node, and includes a CDN Cache device, and then each node constitutes a CDN node system, and each node is managed by an SLB (load balancing) device. The CDN Cache equipment is main function equipment in the node.
In the application, the user side is connected with and communicates with the secondary CDN node server, and specifically, the secondary CDN node server is a node with an optimal distance and is used for reducing transmission time of request data and reducing user waiting time. Preferably, the method comprises the steps of obtaining position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and the user side according to the position information, and determining the secondary CDN node servers according to the distance information.
Another embodiment is that the optimal secondary CDN node server of the back source is determined according to the following formula:
P＝R*T*Tio*C*F/S
wherein S is a geographical distance, R is a disk space available for the CDN server, T is an output bandwidth, Tio is an I/O bandwidth of a disk, C is a processing capacity of a CPU, and F is an idle resource of the CDN node. The larger the P, the larger the selection weight.
And the secondary CDN node server acquires a data request of the user side according to the connection relation between the secondary CDN node server and the user side, searches corresponding request data according to the data request and sends the corresponding request data to the user side.
Generally, if a user has requested the requested data, the secondary CDN node server may increase the requested data according to the data request. And the second-level CDN node server inquires and searches the request data from the cache, and when the request data is searched, the request data is sent to a user side for display.
Referring to fig. 3, a first forwarding module 302 is configured to send the data request to a primary CDN node server to search for the requested data and send the requested data to a user side if the data request is not responded.
In this application, if the request data is not applied by the user side, the data will not exist in the secondary CDN server, or the request data is invalid due to too long time, the request data cannot be provided to the user side, and at this time, the secondary CDN node server will not be able to respond to the data request of the user side. Specifically, the data request non-response includes: data not stored, data failed, or data error. The user side refers to any user side connected with the same secondary CDN server.
In a specific operation, the secondary node server sets a preset search time length, and when the preset search time length is exceeded and the data request is not responded, the secondary node server is judged to not respond.
And then, the secondary CDN server sends the data request to a primary CDN server with a direct connection relation with the secondary CDN server, the primary CDN server searches the request data, and sends the request data to a user side.
Referring to fig. 2, in S201, when the primary CDN node server does not respond to the data request, the data request is sent to an adjacent primary CDN server.
If the primary CDN server does not respond, the primary CDN node server is judged to be incapable of providing the request data, so that the search can be continuously carried out from the primary node server adjacent to the primary CDN node server.
Referring to fig. 2, the adjacent one-level CDN server sends the data request to an origin server.
Referring to fig. 3, the second forwarding module 303 is configured to send the data request to an origin server to search for the requested data and send the requested data to a user side if the data request is not responded.
When the first-level CDN node server or an adjacent first-level CDN node server does not respond to the data request, it is determined that the first-level CDN node server or an adjacent first-level CDN node server does not cache the request data and therefore needs to obtain the request data from an origin server, so that the data request is sent to the origin server to search for the request data, and the request data is sent to a user side.
At this time, the primary CDN node server and the secondary CDN node server cache the request data. When the requested data is requested again, it can be obtained from the secondary or primary CDN node server. Preferably, the secondary CDN node server and the primary CDN node server further record load information in real time, and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
After the secondary CDN node server obtains the request data, the type of user side equipment is judged according to the data request of the user, and the data is processed according to the type of the equipment and then sent to the user side for displaying.
Preferably, the secondary CDN node server further includes a history data storage device, and the history data storage device stores a history data and device type and history data correspondence table. After the secondary CDN node server obtains the data request, firstly judging the user terminal device type contained in the data request, searching whether the historical data has the request data corresponding to the user terminal device type requested by the user terminal from the device type and historical data corresponding table according to the device type, if not, returning the source, and if so, sending the historical data to the user terminal.
Claims (10)
1. A back-source method of a CDN node server is characterized by comprising the following steps:
acquiring a data request of a user side according to the connection relation between a secondary CDN node server and the user side, searching corresponding request data according to the data request, and sending the corresponding request data to the user side;
if the data request is not responded, the secondary CDN node server sends the data request to a primary CDN node server to search the request data and send the request data to a user side;
and if the data request is not responded, the primary CDN node server sends the data request to an origin server to search the request data and send the request data to a user side.
2. The method of claim 1, wherein before the data request is sent to the origin server, the method further comprises:
and the primary node server sends the data request to an adjacent primary CDN node server to search for the requested data and send the requested data to a user side.
3. The method of claim 1, wherein the obtaining a data request from a user end according to a connection relationship between a secondary CDN node server and the user end comprises:
the method comprises the steps of obtaining position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and a user side according to the position information, and determining the secondary CDN node servers according to the distance information.
4. The method of claim 1, wherein the data request being unresponsive comprises: data not stored, data failed, or data error.
5. The method of claim 1, wherein the secondary CDN node server and the primary CDN node server record load information in real time and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
6. A back source device of a CDN node server is characterized by comprising:
the source returning module is used for acquiring a data request of the user side according to the connection relation between the secondary CDN node server and the user side, searching corresponding request data according to the data request and sending the corresponding request data to the user side;
the second-level CDN node server is used for searching the request data and sending the request data to a user side;
and the second forwarding module is used for sending the data request to an origin server by the primary CDN node server to search the request data and send the request data to a user side if the data request is not responded.
7. The device of claim 6, wherein the second forwarding module further comprises:
and the parallel forwarding unit is used for sending the data request to an adjacent primary CDN node server by the primary node server to search the request data and send the request data to a user side.
8. The device of claim 6, further comprising:
the position query module is used for acquiring position information of a plurality of secondary CDN node servers, judging distance information between the secondary CDN node servers and the user side according to the position information, and determining the secondary CDN node servers according to the distance information.
9. The device of claim 6, wherein the data request is not responded to comprises: data not stored, data failed, or data error.
10. The device of claim 6, wherein the secondary CDN node server and the primary CDN node server record load information in real-time and forward the data request to an adjacent peer CDN node server when the load information exceeds a preset threshold.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111569130.3A CN114338686A (en) | 2021-12-21 | 2021-12-21 | Source returning method and device of CDN node server |
| PCT/CN2021/141411 WO2023115592A1 (en) | 2021-12-21 | 2021-12-25 | Back-to-source method and apparatus of cdn node server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111569130.3A CN114338686A (en) | 2021-12-21 | 2021-12-21 | Source returning method and device of CDN node server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114338686A true CN114338686A (en) | 2022-04-12 |
Family
ID=81055253
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111569130.3A Pending CN114338686A (en) | 2021-12-21 | 2021-12-21 | Source returning method and device of CDN node server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN114338686A (en) |
| WO (1) | WO2023115592A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115567602A (en) * | 2022-08-15 | 2023-01-03 | 乐视云计算有限公司 | CDN node back-to-source method, device and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110213879A1 (en) * | 2010-03-01 | 2011-09-01 | Ashley Edwardo King | Multi-level Decision Support in a Content Delivery Network |
| CN103457907A (en) * | 2012-05-28 | 2013-12-18 | 中国移动通信集团公司 | Method, equipment and system for multimedia content distribution |
| CN113301071A (en) * | 2020-04-09 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Network source returning method, device and equipment |
| CN113472852A (en) * | 2021-06-02 | 2021-10-01 | 乐视云计算有限公司 | CDN node back-source method, device and equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018098820A1 (en) * | 2016-12-02 | 2018-06-07 | 深圳前海达闼云端智能科技有限公司 | Method and device for sending and receiving data, server, and computer program product |
| CN109542613A (en) * | 2017-09-22 | 2019-03-29 | 中兴通讯股份有限公司 | Distribution method, device and the storage medium of service dispatch in a kind of CDN node |
-
2021
- 2021-12-21 CN CN202111569130.3A patent/CN114338686A/en active Pending
- 2021-12-25 WO PCT/CN2021/141411 patent/WO2023115592A1/en not_active Ceased
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110213879A1 (en) * | 2010-03-01 | 2011-09-01 | Ashley Edwardo King | Multi-level Decision Support in a Content Delivery Network |
| CN103457907A (en) * | 2012-05-28 | 2013-12-18 | 中国移动通信集团公司 | Method, equipment and system for multimedia content distribution |
| CN113301071A (en) * | 2020-04-09 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Network source returning method, device and equipment |
| CN113472852A (en) * | 2021-06-02 | 2021-10-01 | 乐视云计算有限公司 | CDN node back-source method, device and equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115567602A (en) * | 2022-08-15 | 2023-01-03 | 乐视云计算有限公司 | CDN node back-to-source method, device and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2023115592A1 (en) | 2023-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11194719B2 (en) | Cache optimization | |
| US8521851B1 (en) | DNS query processing using resource identifiers specifying an application broker | |
| US9985927B2 (en) | Managing content delivery network service providers by a content broker | |
| US9444759B2 (en) | Service provider registration by a content broker | |
| US11841910B2 (en) | Token-based authentication for a proxy web scraping service | |
| US20120072600A1 (en) | Managing content delivery network service providers | |
| US20230018983A1 (en) | Traffic counting for proxy web scraping | |
| EP4227829A1 (en) | Web scraping through use of proxies, and applications thereof | |
| US7216154B1 (en) | Apparatus and method for facilitating access to network resources | |
| CN114338686A (en) | Source returning method and device of CDN node server | |
| KR100450605B1 (en) | A web application sever and method for providing dynamic contents thereof | |
| WO2023280593A1 (en) | Web scraping through use of proxies, and applications thereof | |
| JP2002024191A (en) | Www system, traffic relief method for www server and www server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220412 |
|
| RJ01 | Rejection of invention patent application after publication |