WO2023123532A1

WO2023123532A1 - Cdn node-based content pushing method and apparatus

Info

Publication number: WO2023123532A1
Application number: PCT/CN2022/070173
Authority: WO
Inventors: 孙涛
Original assignee: 江苏云工场信息技术有限公司
Priority date: 2021-12-30
Filing date: 2022-01-04
Publication date: 2023-07-06
Also published as: CN114338726B; CN114338726A

Abstract

The present application provides a CDN node-based content pushing method and apparatus. The method comprises: a source server acquires a node list of a CDN, sends source data to each CDN node according to the node list and stores the source data; the CDN node acquires a data request of a user side, identifies the device type of the user side according to the data request, and adjusts the source data into easy-to-check data according to the device type of the user side; the easy-to-check data is sent to the user side and stored into the CDN node data cache; and when a data request of any user side having the same device type is received, the easy-to-check data in the data cache is called and sent to the user side. In the present application, the processed source data is stored, the easy-to-check data is directly called when a user side having the same device type requests the source data, the data request frequency is reduced, the load of the source server is relieved, and the data acquisition speed of a user is improved.

Description

A content push method and device based on CDN nodes

technical field

This application requests protection of a data back-to-source technology, and in particular relates to a CDN node-based content push method. The present application also relates to a CDN node-based content pushing device.

Background technique

The principle and function of CDN (Content Distribution Network) is to avoid bottlenecks and links on the Internet that may affect the speed and stability of data transmission, so as to make content transmission faster and more stable. A layer of intelligent virtual network based on the existing Internet is formed by placing CDN node servers all over the network. The CDN system can respond in real time according to the network traffic, the connection of each node, the load status, and the distance to the user. Comprehensive information such as time redirects the user's request to the service node closest to the user. Its purpose is to enable users to obtain the required content nearby, solve the congestion situation of the Internet network, and improve the response speed of users' access to websites.

However, the current CDN node’s response to the client is based on the client’s request. At this time, the CDN node needs to request data from the source server for each client request, resulting in excessive load pressure on the original server and adverse consequences of data delay. Reduce the user's Internet experience.

Contents of the invention

In order to alleviate the problem of high network load pressure on the source server, a content push method based on CDN nodes. The present application also relates to a CDN node-based content pushing device.

This application provides a method for pushing content based on CDN nodes, including:

The source server obtains a CDN node list, sends the source data to each of the CDN nodes according to the node list, and stores the source data;

The CDN node obtains the data request of the client, identifies the device type of the client according to the data request, and adjusts the source data to easy-to-view data according to the device type of the user;

sending the viewable data to the client, and storing the viewable data in the CDN node data cache;

When any client data request of the same device type is received, the viewable data in the data cache is retrieved and sent to any client.

Optionally, also include:

When the CDN node receives the data request from the client, if the easy-to-view data is not found, it calls the stored source data, and adjusts the source data to the easy-to-view data according to the device type of the client. view data;

Sending the viewable data to the client.

Optionally, if the source data expires or cannot be retrieved, request the source data from the upper-level CDN node according to the data request;

If the source data expires at the upper-level CDN node or cannot be retrieved, request the source data from the source server according to the data request.

Optionally, the device type includes: screen size, screen pixels, and screen aspect ratio.

Optionally, the user end includes: a mobile phone, a tablet, a computer, smart glasses, a projector or a smart watch.

The present application also provides a CDN node-based content push device, including:

A data distribution module, used for the source server to obtain a CDN node list, send source data to each of the CDN nodes according to the node list and store the source data;

The data processing module is used for the CDN node to obtain the data request of the client, identify the device type of the client according to the data request, and adjust the source data into easy-to-view data according to the device type of the user;

A data caching module, configured to send the viewable data to the client, and store the viewable data into the CDN node data cache;

The data sending module is configured to call the easily viewable data in the data cache and send it to any client when receiving a data request from any client of the same device type.

Optionally, the data processing module also includes:

When the CDN node receives the data request from the client, if the easy-to-view data is not found, it calls the stored source data, and adjusts the source data to the specified source data according to the device type of the client. easy to view data;

A data sending module, configured to send the easy-to-view data to the client.

Optionally, the data processing module also includes

A data back-to-source unit, configured to request the source data from the upper-level CDN node according to the data request if the source data expires or cannot be retrieved;

The advantages of the present application compared with the prior art are:

The present application provides a content push method based on CDN nodes, comprising: the source server obtains a CDN node list, sends source data to each of the CDN nodes according to the node list and stores the source data; the CDN node Obtaining the data request of the user terminal, identifying the device type of the user terminal according to the data request, adjusting the source data into easy-to-view data according to the user's device type; sending the easy-to-view data to the user terminal, and The easy-to-view data is stored in the CDN node data cache; when any client data request of the same device type is received, the easy-to-view data in the data cache is called and sent to any client . This application stores the source data that has been processed to directly call the easy-to-observe data when there is client source data of the same device type, which greatly reduces the number of data requests, relieves the load on the source server and can improve The speed at which users obtain data improves user experience.

Description of drawings

Figure 1 is a flow chart of content push based on CDN nodes in this application.

Fig. 2 is a flow chart of defining the scope of active transmission of source data in this application.

FIG. 3 is a schematic diagram of a CDN node-based content pushing device in this application.

Detailed ways

The following content is an example of the specific implementation process provided for the technical solution to be protected in this application in detail, but this application can also be implemented in other ways than the description here, and those skilled in the art can follow the guidelines of this application. Below, different technical means are used to realize the present application, so the present application is not limited by the following specific examples.

Please refer to FIG. 1 , S101 The source server obtains a CDN node list, sends source data to each of the CDN nodes according to the node list, and stores the source data.

The CDN node includes a first-level CDN node and a second-level CDN node, the first-level CDN node is connected to the second-level CDN node and the source server, and obtains source data in the source server, and sends the source data to the second-level CDN node middle.

The secondary CDN node is connected to the user end, receives the user's data request and sends source data to the user end according to the data request. The source data is obtained after data processing is performed on the source data requested by the CDN node server.

Specifically, the source server actively distributes the data to the first-level CDN node and the second-level CDN node, and stores the data in the first-level CDN node and the second-level CDN node. To achieve this purpose, the CDN node server in this application is configured to obtain a storage area from a storage dedicated to storing the source data, including adding an independent source data storage, or setting a source data storage partition in the original storage of the CDN node .

The active distribution of data to the first-level CDN node to obtain the second-level CDN node is determined according to the frequency of data usage at each CDN node. In this application, the data usage frequency refers to the data of each type being acquired by the client within a period of time. times.

A preferred method is that the data usage frequency is the number of times data is requested within the next preset time period after the data is requested by the first client, and the number of requests can be for a second The statistics of the level CDN nodes can also be the statistics of multiple CDN nodes.

When the number of requests exceeds the preset number of requests, it is determined that the data should be actively sent by the source server to each CDN node. Preferably, the area range for sending the data can be processed according to the content type of the data.

Please refer to FIG. 2 , S201 acquires data content type.

The content type of the data is determined by content information, and the content information includes data title, content summary and keywords. The data content information is marked by the data uploader when the data is uploaded, and the content information may be a fixed option selection or a custom content information. The content type of the data determined according to the content information includes: art, music, physics, American style, singing and dancing, etc., and those skilled in the art can set the content type according to the specific application environment.

S202 Determine the regional interest index according to the content type.

The area interest index refers to whether the data will be requested in large quantities in an area. Preferably, according to the geographical environment, the user terminal is divided into areas, which are marked as areas A, B, C, D, ..., N. Then get the rating for each content type for each zone, calculated as follows:

Wherein, the W is the number of times data is acquired within a preset time period, the Z is a constant, the M is the number of secondary CDN nodes in the area, the K is a fixed coefficient, and the P _n is the content type score for the nth region.

The determination method of Z is that the average number of requests received by each secondary CDN within the preset time period does not generate a critical value of load pressure on the source server load, and the determination method of K is that KM is greater than the two The maximum number of data requests for a second-level CDN node within a preset time period.

According to the above formula, when the P _n is higher than the preset score, the source server actively sends the source data to the CDN node in the corresponding area, and stores the source data in the CDN node.

Please refer to FIG. 1 , in S102 the CDN node acquires the data request from the client, identifies the device type of the client according to the data request, and adjusts the source data into easy-to-view data according to the device type of the user.

The easy-to-view data refers to the data that the user can easily view through the terminal equipment, and the easy-to-view data is determined according to the device type of the user end, and the device type refers to a mobile phone, a tablet, a computer, smart glasses, a projector or a smart watch Wait for their display type. Specifically, the display type includes screen size, which indicates the size of the displayable area; screen pixels, which indicates the resolution of the display area; screen aspect ratio, which indicates the length and width distance of the data difference display.

The CDN node that receives the data request from the client is a secondary CDN node, and the secondary CDN node adjusts the source data to easy-to-view data according to the display type of the client.

A preferred implementation method is to re-cut or layout the source data according to the display type to adapt to the display type, for example: if the source data is picture data, then the picture data will be edited according to the display type Cropping to be suitable for viewing by the client; if the source data is graphics and text, rearranging the arrangement of the pictures to be suitable for viewing by the client, and generating easy-to-view data after processing the source data.

Referring to FIG. 1 , S103 sends the viewable data to the client, and stores the viewable data into the CDN node data cache.

After the easy-to-view data is generated, the easy-to-view data will be sent to the client corresponding to the request information for processing by the user. Before that, the observable data will be cached for a long time to be provided to other client requests.

The relationship between the client and the secondary CDN node is that a secondary CDN node is connected to multiple client terminals, and each client terminal may be of the same type or of a different type. When a user end requests a data and obtains the easy-to-view data, the easy-to-view data may also be requested by other user ends, so it is necessary to store the easy-to-view data, but the memory of the CDN node is limited, so In this application, the secondary CDN node is bound to the client to a certain extent, that is, a common client table is established in the CDN node, and the common client table records each client that has requested data from the CDN node , and record the display type of the user terminal, and cache the corresponding easy-to-view data according to the display type corresponding to the common user terminal table.

Please refer to FIG. 1, S104, when receiving any client data request of the same type of device, retrieve the easily viewable data in the data cache and send it to any client.

After completing the caching of the easy-to-view data, after receiving a data request from a client of the same device type, the cached data can be retrieved and sent to the client. When the CDN node receives the data request from the client , if the easy-to-view data is not found, the stored source data is called, and the source data is adjusted to the easy-to-view data according to the device type of the user end; the easy-to-view data is sent to the user end . Preferably, when the cached data is invalid, expired or cannot be retrieved, the source data stored by the CDN node is extracted, and the source data is re-edited to generate easy-to-view data and sent to the client. If the source data cannot be hit by the secondary CDN node, the source data is obtained from the upper-level CDN node of the secondary CDN node. If the source data cannot be found in the secondary CDN node, the source data is obtained from the source server. The source server is the most fundamental server of the CDN system and must have the source data.

The present application also provides a content pushing device based on a CDN node, including: a data distribution module 301 , a data processing module 302 , a data caching module 303 , and a data sending module 304 .

Referring to FIG. 3 , the data distribution module 301 is used for the source server to obtain a CDN node list, send source data to each of the CDN nodes according to the node list, and store the source data.

Please refer to FIG. 2 , S201 acquires data content type.

S202 Determine the regional interest index according to the content type.

Please refer to FIG. 3, the data processing module 302 is used for the CDN node to obtain the data request of the user end, identify the device type of the user end according to the data request, and adjust the source data to easy according to the user's device type. View data.

Referring to FIG. 3 , the data caching module 303 is configured to send the viewable data to the client, and store the viewable data in the CDN node data cache.

Please refer to FIG. 3 , the data sending module 304 is configured to call the easily viewable data in the data cache and send it to any client when receiving a data request from any client of the same device type.

Claims

A method for pushing content based on CDN nodes, characterized in that it includes:

The source server obtains a CDN node list, sends the source data to each of the CDN nodes according to the node list, and stores the source data;

The CDN node obtains the data request of the client, identifies the device type of the client according to the data request, and adjusts the source data to easy-to-view data according to the device type of the user;

sending the viewable data to the client, and storing the viewable data in the CDN node data cache;

When any client data request of the same device type is received, the viewable data in the data cache is retrieved and sent to any client.
The method for pushing content based on CDN nodes according to claim 1, further comprising:

When the CDN node receives the data request from the client, if the easy-to-view data is not found, it calls the stored source data, and adjusts the source data to the easy-to-view data according to the device type of the client. view data;

Sending the viewable data to the client.
According to the content push method based on CDN nodes according to claim 1, it is characterized in that, if the source data expires or cannot be hit, then request the source data to the superior CDN node according to the data request;

If the source data expires at the upper-level CDN node or cannot be retrieved, request the source data from the source server according to the data request.
The method for pushing content based on a CDN node according to claim 1, wherein the device type includes: screen size, screen pixels, and screen aspect ratio.
The method for pushing content based on a CDN node according to claim 1, wherein the client includes: a mobile phone, a tablet, a computer, smart glasses, a projector or a smart watch.
A CDN node-based content push device is characterized in that it includes:

A data distribution module, used for the source server to obtain a CDN node list, send source data to each of the CDN nodes according to the node list and store the source data;

The data processing module is used for the CDN node to obtain the data request of the client, identify the device type of the client according to the data request, and adjust the source data into easy-to-view data according to the device type of the user;

A data caching module, configured to send the viewable data to the client, and store the viewable data into the CDN node data cache;

The data sending module is configured to call the easily viewable data in the data cache and send it to any client when receiving a data request from any client of the same device type.
The CDN node-based content pushing device according to claim 6, wherein the data processing module further comprises:

When the CDN node receives the data request from the client, if the easy-to-view data is not found, it calls the stored source data, and adjusts the source data to the specified source data according to the device type of the client. easy to view data;

A data sending module, configured to send the easy-to-view data to the client.
The CDN node-based content push device according to claim 6, wherein the data processing module further includes

A data back-to-source unit, configured to request the source data from the upper-level CDN node according to the data request if the source data expires or cannot be retrieved;

If the source data expires at the upper-level CDN node or cannot be retrieved, request the source data from the source server according to the data request.
The device for pushing content based on CDN nodes according to claim 6, wherein the device type includes: screen size, screen pixels, and screen aspect ratio.
The CDN node-based content pushing device according to claim 6, wherein the client includes: a mobile phone, a tablet, a computer, smart glasses, a projector or a smart watch.