Data access method and device in content distribution network, equipment and storage medium

By judging and draining quality non-sensitive requests in the CDN, the problem of underutilization of CDN resources is solved, and the resource waste is maximized is achieved.

CN118921406AActive Publication Date: 2024-11-08BEIJING VOLCANO ENGINE TECH CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202410915971.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-09
Publication Date
2024-11-08
Estimated Expiration
2044-07-09

AI Technical Summary

Technical Problem

In the content distribution network (CDN), requests that do not meet the preset quality of service conditions cannot be diverted to the self-built CDN, resulting in waste of resources and underutilized self-built CDN resources.

Method used

By determining whether the data access request is a quality non-sensitive request, and when certain conditions are met, it is diverted to the self-built CDN node, thereby achieving the maximum utilization of the self-built node resources. The specific method includes the client judging the request type, the server and the CDN device work together, generating and passing the access address of the self-built node so that the client can obtain the required data.

Benefits of technology

Effectively utilize the redundant resources of self-built CDN, reduce resource waste, improve resource utilization, and avoid resource idle problems caused by excessive constraints.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921406A_ABST
    Figure CN118921406A_ABST
Patent Text Reader

Abstract

The invention discloses a data access method in a content distribution network, and the method comprises the steps: judging whether a data access request is a quality-insensitive request or not after a client obtains the data access request, and transmitting the data access request to a server if the data access request is the quality-insensitive request, so as to request the server for the address of a self-built node in the CDN; after receiving the data access request, the server requests the CDN device to obtain the sub-domain name of the self-built node, then generates the access address of the self-built node according to the sub-domain name of the self-built node, namely the first access address, and sends the first access address to the client, so that the client obtains the data to be accessed through the first access address. Namely, when the client side drains the flow to the self-built node, the quality is considered, but the quality is not strictly controlled, so that more quality-insensitive requests can be guided to the self-built node, redundant resources in the self-built node are fully utilized, maximum utilization of the resources is realized, and resource waste is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a data access method, device, equipment and storage medium in a content distribution network. Background Art

[0002] For some applications that target global users, in order to better meet user needs and reduce access delays, service providers that provide the application usually deploy servers in areas closer to users to provide a faster access experience. To further improve access speed, service providers reduce the load on source servers by building their own content delivery networks (CDNs). Self-built CDNs refer to a network of servers distributed in multiple geographical locations that service providers build and manage themselves to accelerate the transmission and access of content (such as web pages, images, videos, etc.).

[0003] However, in some application scenarios, constraints are set to switch requests to the self-built CDN. Requests that do not meet the preset conditions cannot be directed to the self-built CDN, resulting in a waste of self-built CDN resources. Summary of the invention

[0004] In view of this, embodiments of the present application provide a method, apparatus, device and storage medium for accessing data in a content distribution network to fully utilize self-built resources.

[0005] To achieve the above purpose, the technical solutions provided by the embodiments of the present application are as follows:

[0006] In a first aspect of the present application, a method for accessing data in a content distribution network is provided, the method being applied to a client and comprising:

[0007] Get data access request;

[0008] If it is determined that the data access request is a quality-insensitive request, sending the data access request to the server, wherein the data access request is used to request an access address of a self-built node corresponding to a content delivery network CDN;

[0009] If the self-built node can be accessed, the first access address sent by the server is received, and the data to be accessed is obtained according to the first access address, where the first access address is the access address of the target self-built node

[0010] In a second aspect of the present application, a method for accessing data in a content distribution network is provided, the method being applied to a server, comprising:

[0011] Receive a data access request sent by a client, where the data access request is used to request an access address of a self-built node;

[0012] If the self-built node can be accessed, the data access request is sent to the CDN device, where the data access request includes the first primary domain name, where the first primary domain name is the primary domain name used to access the self-built node;

[0013] Receiving a subdomain name of a target self-built node sent by the CDN device, and generating a first access address based on the first primary domain name and the subdomain name;

[0014] The first access address is sent to the client, so that the client obtains the data to be accessed based on the first access address.

[0015] In a third aspect of the present application, a method for accessing data in a content distribution network is provided, the method being applied to a CDN device, comprising:

[0016] Receive a data access request sent by the server, where the data access request is used to request a subdomain name of a node to be accessed;

[0017] If the self-built node can be accessed, the target self-built node is determined from at least one self-built node according to the data access request, and the subdomain name corresponding to the target self-built node is sent to the server, so that the server generates a first access address according to the primary domain name of the target self-built node and the subdomain name, and sends the first access address to the client.

[0018] In a fourth aspect of the present application, a data access device in a content distribution network is provided, the device being applied to a client and comprising:

[0019] A processing unit, configured to obtain a data access request;

[0020] A sending unit, configured to send the data access request to a server if it is determined that the data access request is a quality-insensitive request, wherein the data access request is used to request an access address of a self-built node corresponding to a content delivery network CDN;

[0021] a receiving unit, configured to receive a first access address sent by the server if the self-built node can be accessed, and obtain the data to be accessed according to the first access address, wherein the first access address is the access address of the target self-built node,

[0022] In a fifth aspect of the present application, a data access device in a content distribution network is provided, the device being applied to a server, comprising:

[0023] A receiving unit, used to receive a data access request sent by a client, wherein the data access request is used to request an access address of a self-built node;

[0024] A sending unit, configured to send the data access request to the CDN device if the self-built node can be accessed, wherein the data access request includes a first primary domain name, and the first primary domain name is a primary domain name used to access the self-built node;

[0025] The receiving unit is further configured to receive the subdomain name of the target self-built node sent by the CDN device;

[0026] A processing unit, configured to generate a first access address using the first primary domain name and the subdomain name;

[0027] The sending unit is further configured to send the first access address to the client, so that the client obtains the data to be accessed based on the first access address.

[0028] In a sixth aspect of the present application, a data access device in a content distribution network is provided, the device being applied to a CDN device, comprising:

[0029] A receiving unit, used to receive a data access request sent by a server, wherein the data access request is used to request a subdomain name of a node to be accessed;

[0030] a processing unit, configured to determine a target self-built node from at least one self-built node according to the data access request if the self-built node can be accessed;

[0031] The sending unit is used to send the subdomain name corresponding to the target self-built node to the server, so that the server generates a first access address according to the primary domain name of the target self-built node and the subdomain name, and sends the first access address to the client.

[0032] In the seventh aspect of the present application, an electronic device is provided, comprising: a processor and a memory; the memory is used to store instructions or computer programs; the processor is used to execute the instructions or computer programs in the memory, so that the electronic device executes the method described in the first aspect, the second aspect or the third aspect.

[0033] In an eighth aspect of the present application, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the instructions are executed on a device, the device executes the method described in the first aspect, the second aspect, or the third aspect.

[0034] In the ninth aspect of the present application, a computer program product is provided, wherein the computer program product comprises a computer program / instructions, and when the computer program / instructions are executed by a processor, the method described in the first aspect, the second aspect or the third aspect is implemented.

[0035] It can be seen that the embodiments of the present application have the following beneficial effects:

[0036] In the present application, after obtaining a data access request, the client determines whether the data access request is a quality-insensitive request. If so, it sends a data access request to the server to request the address of the self-built node in the CDN. After receiving the data access request, the server requests the CDN device to obtain the subdomain name of the self-built node, and then generates an access address of the self-built node according to the subdomain name of the self-built node, that is, the first access address, and sends the first access address to the client so that the client can obtain the data to be accessed through the first access address. That is, in the present application, when directing traffic to the self-built node, the client takes the quality into consideration but does not strictly control the quality, so that more quality-insensitive requests can be directed to the self-built node, so as to make full use of the redundant resources in the self-built node, maximize the utilization of resources, and avoid waste of resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0038] Figure 1 An interactive diagram of a data access method in a content distribution network provided by an embodiment of the present application;

[0039] Figure 2 A schematic diagram of data access in a scenario of lowering resource rated capacity provided by an embodiment of the present application;

[0040] Figure 3 A data access schematic diagram of disabling the ability to access self-built nodes provided in an embodiment of the present application;

[0041] Figure 4 Another data access schematic diagram for disabling the ability to access self-built nodes provided in an embodiment of the present application;

[0042] Figure 5-Figure 7 A flow chart of a method for accessing data in a content distribution network provided in an embodiment of the present application;

[0043] Figure 8-10 A schematic diagram of the structure of a data access device in a content distribution network provided by an embodiment of the present application;

[0044] Fig.11 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] Video on Demand (VOD) is a service that allows users to select and watch video content at any time. Users can watch content on demand through the Internet or other digital transmission methods. In order to transmit video content to users quickly and stably, video on demand services usually use CDN to cache content on edge servers around the world. When a user requests a video, CDN will route the request to the edge server closest to the user, thereby reducing latency and improving playback quality.

[0047] Typically, when users initiate on-demand requests through a client (such as a web page, mobile app, or smart TV), the video on demand service provider will process these requests. Request processing includes verifying user identity, checking subscription status, obtaining user device information and network conditions, etc. Based on this information, the service provider will select the appropriate video format and resolution, as well as the best edge server. Video on demand services transmit video content to users in segments through streaming protocols such as HTTP Live Streaming (HLS) or Dynamic Adaptive Streaming over HTTP (DASH). These protocols support Adaptive Bitrate (ABR) technology, which can adjust the video quality in real time according to the user's network conditions to ensure smooth playback.

[0048] The client on the user's device receives the video segments, decodes them and plays them. The client can initiate new requests to the service based on user operations (such as pause, fast forward, rewind, etc.) to achieve on-demand viewing.

[0049] At present, in order to ensure the full utilization of node resources in the self-built CDN, it is considered to direct data access requests to the nodes of the self-built CDN. Usually, before directing the traffic, it is determined whether the data access request meets the corresponding service quality indicators. If it does, the data access request is directed to the self-built CDN. This operation will limit the number of diversions, resulting in the node resources in the self-built CDN not being fully utilized, resulting in resource waste. Among them, judging whether the data access request meets the service quality indicators means that according to the data access request, the network and system are continuously measured and monitored to collect data about the service quality, and the collected data related to the service quality is compared with the pre-set service quality standards.

[0050] Based on this, the present application provides a data access processing method in a content distribution network, which balances resource waste and quality constraints, and maximizes the diversion of self-built nodes under the condition of considering quality. Specifically, data access requests that are not sensitive to quality (do not need to strictly meet quality constraints) are diverted to self-built nodes, thereby achieving effective utilization of redundant resources in self-built nodes and reducing resource waste.

[0051] Among them, self-built nodes refer to nodes in self-built CDN, usually referring to servers or server clusters distributed in different geographical locations, which are used to store and cache static content and / or dynamic content (such as pictures, videos, CSS files, etc.), and can quickly respond to user requests.

[0052] It should be noted that the CDN in this application is a fusion CDN, which generally refers to the integration of services from multiple different CDN providers to leverage their respective strengths to improve the overall content distribution network performance and reliability. Among them, the fusion CDN includes self-built CDNs, which include self-built CDNs overseas. Self-built CDNs overseas generally refer to the establishment of data centers or server facilities in one or more regions overseas. By establishing CDNs in multiple regions, it is possible to be closer to global users, thereby improving the response speed and quality of services and reducing data transmission delays. At the same time, through the deployment of self-built CDNs, load balancing, traffic diversion, etc. can be achieved to improve the stability and reliability of services.

[0053] It should be noted that in order to distinguish between resource scheduling in the case of self-built CDN and resource scheduling in the case of no self-built CDN, the previous scheduling scenario is called fusion scheduling, and the latter scheduling scenario is called normal scheduling. In the fusion scheduling scenario, the resources of the self-built nodes can be scheduled. Among them, the main domain names corresponding to normal scheduling and fusion scheduling are different, but the subdomain names of non-self-built nodes corresponding to the two scenarios can be the same. For example, the main domain name under normal scheduling is x1, and its corresponding subdomain names include a1, a2 and a3; the main domain name under fusion scheduling is x2, and its corresponding subdomain names include a1, a2, a3 and b1. Among them, b1 is the subdomain name of the self-built node.

[0054] Whether it is normal scheduling or fusion scheduling, weights can be configured for different nodes (self-built nodes and non-self-built nodes) to guide traffic to the nodes according to the weights. For example, under normal scheduling, the weight of the non-self-built nodes corresponding to a1 is 40%, the weight of the non-self-built nodes corresponding to a2 is 50%, and the weight of the non-self-built nodes corresponding to a3 is 10%. For another example, under fusion scheduling, the weight of the non-self-built nodes corresponding to a1 is 8%, the weight of the non-self-built nodes corresponding to a2 is 10%, the weight of the non-self-built nodes corresponding to a3 is 2%, and the weight of the self-built nodes corresponding to b1 is 80%.

[0055] To facilitate understanding of the technical solution of the present application, an explanation will be given below with reference to the accompanying drawings.

[0056] See also Figure 1 , which is a flowchart of data access processing interaction in a content distribution network provided by an embodiment of the present application, such as Figure 1 As shown, the method includes:

[0057] S101: The client obtains a data access request.

[0058] In this embodiment, the client can detect in real time the operations triggered by the user on the client, such as refreshing the video stream, playing the video, fast forwarding, replaying, etc. When the operation triggered by the user is detected, a data access request matching the operation is generated.

[0059] The data access request may include the location information of the user device and the operator. The operator refers to a company that provides communication services in the communication industry, also known as a telecommunications operator or telecommunications service provider.

[0060] After generating a data access request, the client determines whether the data access request is a quality-insensitive request. If so, S102 is executed. Quality-insensitive means that fluctuations or reductions in quality can be tolerated to a certain extent without causing excessive impact on user experience, thereby helping to optimize resource allocation. The specific performance of quality is closely related to the business. For example, for a video request business, the quality may include parameters such as video resolution, frame rate, audio clarity, freeze rate, and start rate.

[0061] A quality-insensitive request means that the quality of the request is not critical to the user experience, or that some quality degradation can be tolerated to a certain extent. For example, for a video-on-demand request, quality-insensitive may include accepting reduced video quality to a certain extent without affecting the user experience even when the network conditions are poor or the server load is high.

[0062] Specifically, whether a data access request is a quality-insensitive request can be determined in the following ways, including:

[0063] If the service corresponding to the data access request is not a video playback service, the data access request may be directly determined as a quality-insensitive request.

[0064] If the service corresponding to the data access request is a video playback service, then if the data access request is used to request non-first frame data of the video, the amount of data stored in the video buffer for the video is obtained; if the amount of data meets the preset conditions, the data access request is determined to be a quality-insensitive request. Among them, the amount of data meets the preset conditions, indicating that the player has pre-loaded enough data into the video buffer, thereby ensuring smooth playback and reducing playback freezes and interruptions caused by network delays or jitters. Among them, the preset conditions can be set according to the actual application situation, and this embodiment is not limited here.

[0065] Specifically, if the data volume makes the difference between the value of the service quality indicator corresponding to the client when playing the video and the required value less than or equal to the preset threshold, the data access request is determined to be a non-quality sensitive request. In other words, if the data volume makes the service quality indicator corresponding to the client when playing the video not change much, the data access request is determined to be a non-quality sensitive request.

[0066] Among them, service quality indicators may include the freeze rate, start rate, etc. The freeze rate refers to the frequency of video pauses or freezes due to insufficient buffering during video playback. When the video player cannot obtain enough data in time during playback (for example, due to slow or unstable network speed), freezes will occur. The start rate refers to the ratio of the video to load and start playing quickly when the user starts playing the video. In other words, it measures how quickly the user can see the video content start playing after clicking play.

[0067] S102: If it is determined that the data access request is a quality-insensitive request, the client sends a data access request to the server.

[0068] In this embodiment, after determining that the data access request is a quality-insensitive request, the client may mark the data access request so as to direct the data access request to the self-built node.

[0069] In actual applications, in order to distinguish between data access requests in common scenarios and data access requests under fusion scheduling, when a data access request is used to request the access address of a self-built node corresponding to a CDN, an identifier can be added to the data access request, and the identifier facilitates the server to identify that the data access request is used to request the access address of a self-built node. Alternatively, there is always an identifier field in the data access request, and when the value of the identifier field is the first value, it is used to request the access address of a self-built node; when the value of the identifier is the second value, it is used to request the access address of a non-self-built node.

[0070] S103: The server sends a data access request to the CDN device.

[0071] In this embodiment, the server has the ability to provide access to self-built nodes. Under normal circumstances, this ability is in an enabled state, so that the address of the self-built node can be provided to the client. When the self-built node is overloaded or fails, the above ability can be controlled to be in a disabled state, so as to provide the client with the address of the non-self-built node.

[0072] The data access request sent by the server to the CDN device may include the location and the first primary domain name. The first primary domain name is the primary domain name used to access the self-built node. In this embodiment, the server can maintain different primary domain names, including the primary domain name (first primary domain name) of the fusion scheduling and the primary domain name (second primary domain name) under the normal scheduling. When the server perceives that the data access request is to access the self-built node, the first primary domain name will be added to the data access request so that the CDN device can provide the subdomain name of the self-built node.

[0073] The CDN device can distribute data access requests to different server nodes in the CDN network to ensure that the data access requests can be responded to quickly and efficiently. Specifically, the CDN device can make intelligent selections based on factors such as server load and geographical location.

[0074] It should be noted that when the server-side access to self-built nodes is enabled, the data access request sent to the CDN device carries the first primary domain name. When the server-side access to self-built nodes is disabled, the data access request sent to the CDN device carries the second primary domain name.

[0075] S104: If the self-built node is accessible, the CDN device determines a target self-built node from at least one self-built node according to the data access request, and sends a subdomain name corresponding to the target self-built node to the server.

[0076] In this embodiment, the CDN device has the ability to provide access to self-built nodes. Under normal circumstances, this ability is in an enabled state, so that the server can be provided with the subdomain name required to access the self-built node. When the self-built node is overloaded or fails, the above ability can be controlled to be in a disabled state, so as to provide the server with the subdomain name to access the non-self-built node.

[0077] Specifically, if the data access request carries the first primary domain name for accessing the self-built node and the capability on the CDN device side is in the turned-on state, after receiving the data access request forwarded by the server, the CDN device will determine the target self-built node with redundant resources from at least one self-built node it manages, and send the subdomain name of the target self-built node to the server.

[0078] Among them, the CDN device determines the target self-built node from at least one self-built node according to the data access request, including: determining at least one self-built node corresponding to the location information according to the location information in the data access request; determining the self-built node with redundant resources as the target self-built node according to the resource rating and actual resource usage corresponding to the self-built node. When there are multiple self-built nodes with redundant resources, the self-built node with the most redundant resources can be determined as the target self-built node. Alternatively, the multiple self-built nodes are all determined as target self-built nodes so as to guide traffic to each target self-built node according to a pre-configured weight. For example, the data access request or the bandwidth used corresponding to the data access request can be guided to different self-built nodes according to the preset weight.

[0079] In this embodiment, each self-built node can report its own resource rating and actual resource usage to the CDN device. When the CDN device receives the data access request sent by the server, it will determine whether the self-built node has sufficient redundant resources for the client to access based on the resource rating and actual resource usage corresponding to the self-built node. If there are sufficient redundant resources, the self-built node will be determined as the target self-built node, and the subdomain name of the target self-built node will be sent to the server.

[0080] The resource quota refers to the maximum amount of resources allowed to be used, and the subdomain is a more specific identifier created under the main domain name, which is usually used to organize and manage different parts or services of a website. It is defined by adding a name and a dot before the main domain name. For example, under the main domain name example.com, blog.example.com and shop.example.com are subdomains.

[0081] In this embodiment, the CDN device manages the subdomain name of each self-built node, and after determining the target self-built node, sends the subdomain name of the target self-built node to the server.

[0082] S105: The server generates a first access address according to the first main domain name and the subdomain name.

[0083] S106: The server sends the first access address to the client.

[0084] In this embodiment, the server manages or maintains the schedulable primary domain names (including the primary domain names of self-built nodes and the primary domain names of non-self-built nodes). After receiving the subdomain name of the target self-built node sent by the relevant equipment of the CDN, the server uses the primary domain name and subdomain name of the self-built node to generate a first access address, and sends the first access address to the client.

[0085] The first access address may be a uniform resource location (URL), and the complete URL consists of a protocol (such as HTTP or HTTPS), a subdomain name, a primary domain name, a port number (optional), a path, a query parameter, and a fragment.

[0086] S107: The client obtains the data to be accessed according to the first access address.

[0087] The first access address is used to point to the target self-built node. After receiving the first access address, the client will use the first access address to access the target self-built node to obtain the data to be accessed from the target self-built node.

[0088] It can be seen that the client can direct data access requests that are not sensitive to quality (no need to strictly meet quality constraints) to self-built nodes, thereby achieving effective utilization of redundant resources in self-built nodes and reducing resource waste.

[0089] In some scenarios, the self-built nodes may be overloaded or fail. To ensure the normal operation and service quality of the self-built nodes, you can take the following measures:

[0090] The first method is that the CDN device lowers the resource rating of the self-built node. That is, it lowers the resource rating of the self-built node, thereby reducing traffic and alleviating the load on the self-built node. Specifically, the self-built node can actively lower its own resource rating and report the lowered resource rating to the CDN device, which then updates the resource rating of the self-built node it maintains.

[0091] For example, Figure 2 The application scenario diagram shown in the figure shows that in this scenario, the self-built node actively reduces the resource rating and reports the reduced resource rating and actual resource usage to the CDN device. The client sends the data access request to the CDN device through the server. The CDN device determines the appropriate self-built node based on the resource rating and actual resource usage reported by each node, and feeds back the subdomain name of the self-built node to the server.

[0092] It should be noted that Figure 2 The specific implementation of each step can be found in Figure 1 The relevant descriptions in the method embodiment will not be repeated in this embodiment.

[0093] The second way is that the ability to access self-built nodes is in a closed state. This way includes the following situations: One situation is that the CDN device side closes the mechanism for accessing self-built nodes, thereby cutting off the scheduling of redundant resources in self-built nodes. Another situation is that the server side's ability to access self-built nodes is in a closed state. In this case, after receiving the data access request sent by the client, the server adds a second primary domain name to the data access request before forwarding the data access request to the relevant equipment of the CDN, so as to obtain the subdomain name of the non-self-built node through the relevant equipment of the CDN. In another situation, the ability of both the CDN device side and the server side to access self-built nodes is in a closed state.

[0094] For example, Figure 3In the application scenario shown, in this scenario, if the CDN device turns off the ability to call the self-built node but the server does not turn it off, the server can still send the data access request including the first primary domain name to the CDN device. In this case, since the ability to call the self-built node in the relevant CDN device is turned off, the subdomain name of the non-self-built node is returned, so that the server generates a second access address for accessing the non-self-built node based on the first primary domain name and the subdomain name of the non-self-built node, and returns the second access address to the client.

[0095] exist Figure 4 In the application scenario shown, if the server turns off the ability to call the self-built node, regardless of whether the CDN device turns off the ability to call the redundant resources in the self-built node, the server carries the second primary domain name in the data access request sent to the CDN device. The CDN device obtains the subdomain name of the non-self-built node based on the data access request, so that the server generates an access address for accessing the non-self-built node based on the second primary domain name and the subdomain name, that is, the second access address, so as to send the second access address to the client.

[0096] It should be noted that Figure 3 and Figure 4 The specific implementation of the relevant steps can be found in the above Figure 1 The relevant descriptions in the above embodiments will not be repeated in this embodiment.

[0097] The overload of the self-built node may refer to the actual usage of the redundant computer room's resources being greater than the preset usage threshold. For example, the rated bandwidth of the self-built node is 500G and the preset usage threshold is 430G. When the actual usage exceeds 430G, the self-built node is determined to be overloaded. Alternatively, if the difference between the rated amount of the self-built node's resources and the actual usage of the resources is less than the preset value, the redundant computer room is determined to be overloaded.

[0098] Generally speaking, when a self-built node is overloaded or fails, the first method is used first. If the first method cannot solve the above situation, the second method is used.

[0099] In this embodiment, for the server, when the self-built node cannot be accessed, a second access address is sent to the client, so that the client obtains the data to be accessed according to the second access address. The second access address is the access address of the non-self-built node. Specifically, when the self-built node cannot be accessed, the subdomain name of the non-self-built node sent by the CDN device is received, and the second access address is generated according to the main domain name and subdomain name of the non-self-built node.

[0100] Among them, the inability to access self-built nodes can include:

[0101] One is that the server detects that the ability to access the self-built node configured by itself is in a closed state. That is, after detecting that the ability to access the redundant computer room is closed, the CDN device on the server forwards the data access request including the second primary domain name, and thus cannot obtain the subdomain name of the self-built node.

[0102] The other is that the CDN device's ability to access self-built nodes is disabled. In specific implementation, the data access request forwarded by the server to the CDN device still carries the first primary domain name for accessing the self-built node. After receiving the data access request, the CDN device returns the subdomain name of the non-self-built node to the server.

[0103] Another situation is that the redundant resources of all self-built nodes cannot meet the bandwidth required by the data access request. That is, the remaining resources of the self-built nodes are not enough to support the data access request. In this case, the data access request forwarded by the server to the CDN device still carries the first primary domain name for accessing the self-built node, and the CDN device returns the subdomain name of the non-self-built node to the server.

[0104] It can be seen that in this application, when the client directs traffic to the self-built node, the quality is considered but the quality is not strictly controlled, so that more quality-insensitive requests can be directed to the self-built node to make full use of the redundant resources in the self-built node, maximize the utilization of resources, and avoid resource waste.

[0105] See also Figure 5 , which is a flow chart of a data access method in a content distribution network provided by an embodiment of the present application, such as Figure 5 As shown, the method is applied to the client and includes:

[0106] S501: Obtain a data access request.

[0107] In this embodiment, when a user browses multimedia resources through a client, a corresponding operation may be triggered for the multimedia resources, and the client generates a data access request based on the triggered operation. The multimedia resources may include resources such as videos and pictures.

[0108] S502: If it is determined that the data access request is a quality-insensitive request, send the data access request to the server.

[0109] When the data access request is a quality-insensitive request, the data access request is at least used to request the access address of the self-built node corresponding to the CDN.

[0110] When the service type corresponding to the data access request is different, the way of determining whether the data access request is a quality-insensitive request is different. When the service corresponding to the data access request is a non-video playback service, the data access request is directly determined to be a quality-insensitive request. When the service corresponding to the data access request is a video playback service, if the data access request is used to request non-first frame data of the video, the amount of data stored in the video buffer for the video is obtained; if the data amount meets the preset conditions, the data access request is determined to be a quality-insensitive request.

[0111] Specifically, if the data volume makes the difference between the actual value of the service quality indicator corresponding to the client when playing the video and the required value of the service quality indicator corresponding to the video less than or equal to a preset threshold, the data access request is determined to be a quality-insensitive request.

[0112] For the specific implementation of determining that the data access request is a quality-insensitive request, reference may be made to the relevant description of S101 in the above method embodiment.

[0113] S503: If the self-built node can be accessed, a first access address sent by the server is received, and data to be accessed is obtained according to the first access address.

[0114] The first access address is the access address of the target self-built node, and the target self-built node can be a self-built node with redundant self-built nodes among at least one self-built node corresponding to the CDN. Specifically, the first access address is generated by the server end according to the subdomain name of the target self-built node obtained from the CDN device according to the data access request.

[0115] In some scenarios, if the self-built node cannot be accessed, the second access address sent by the server is received, and the data to be accessed is obtained according to the second access address. The second access address is the access address of the non-self-built node. The inability to access the self-built node includes: the ability of the server and / or CDN device to access the self-built node is closed, or the redundant resources of the self-built node are insufficient to support the data access request.

[0116] See also Figure 6 , which is a flow chart of a data access method in a content distribution network provided by an embodiment of the present application, such as Figure 6 As shown, the method is applied to the server, including:

[0117] S601: Receive a data access request sent by a client, where the data access request is used to request an access address of a self-built node.

[0118] S602: If the self-built node can be accessed, a data access request is sent to the CDN device.

[0119] In this embodiment, after receiving a data access request sent by the client, if the server detects that the data access request is used to request an access address of a self-built node, a first primary domain name is added to the data access request, and the first primary domain name is the primary domain name used to access the self-built node.

[0120] S603: Receive the subdomain name of the target self-built node sent by the CDN device, and generate a first access address based on the first primary domain name and the subdomain name.

[0121] The target self-built node is a self-built node with redundant resources among at least one self-built node corresponding to the CDN device, and the target self-built node is a self-built node that can allow the data access request to access determined by the CDN device from at least one self-built node according to the data access request. After determining the target self-built sub-node, the CDN device sends the sub-domain name of the target self-built node to the server, so that the server generates the first access address according to the first main domain name and the sub-domain name.

[0122] S604: Send a first access address to the client, so that the client obtains data to be accessed based on the first access address.

[0123] After the server generates the first access address, it sends the first access address to the client so that the client can use the first access address to obtain required data.

[0124] When the self-built node cannot be accessed, the server sends a second access address to the client, so that the client obtains the required access data according to the second access address, wherein the second access address is an address corresponding to the non-self-built node.

[0125] Specifically, if the ability of the CDN device to access the self-built node is in a closed state or the redundant resources of the self-built node are insufficient to support the data access request, receive the subdomain name of the non-self-built node sent by the CDN device; generate a second access address based on the first primary domain name and the subdomain name; and send the second access address to the client.

[0126] If the ability to access the self-built node on the server device is in a closed state, the data access request includes a second primary domain name, which is the primary domain name used when accessing a non-self-built node; receiving the subdomain name of the non-self-built node sent by the CDN device; generating a second access address based on the second primary domain name and the subdomain name; and sending the second access address to the client.

[0127] It should be noted that, for the specific implementation of each step in this embodiment, reference may be made to the relevant descriptions in S103, S105, and S106 above.

[0128] See also Figure 7, which is a flow chart of a data access method in a content distribution network provided by an embodiment of the present application, the method is applied to a CDN device, and includes:

[0129] S701: Receive a data access request sent by a server, where the data access request is used to request a subdomain name of a node to be accessed.

[0130] In this embodiment, after receiving the data access request sent by the client, the server forwards the data access request to the CDN device.

[0131] Specifically, if the ability of the server to access the self-built node is turned on, the data access request it sends to the CDN device includes the first primary domain name; if the ability of the server to access the self-built node is turned off, the data access request it sends to the CDN device includes the second primary domain name.

[0132] S702: If the self-built node is accessible, determine a target self-built node from at least one self-built node according to the data access request, and send a subdomain name corresponding to the target self-built node to the server.

[0133] In this embodiment, if the data access request carries the first primary domain name and the CDN device's ability to access self-built nodes is enabled, a target self-built node is determined from at least one self-built node, and the subdomain name of the target self-built node is sent to the server. The target self-built node refers to a self-built node with redundant resources, which can be one or more.

[0134] Specifically, the CDN device will determine at least one self-built node corresponding to the location information according to the location information in the data access request; and determine the self-built node with redundant resources as the target self-built node according to the resource rating and actual resource usage corresponding to the self-built node. The self-built node can regularly report its own resource rating and actual resource usage to the CDN device, so that the CDN device can accurately grasp the load of the self-built node and avoid overloading of the self-built node.

[0135] When it is detected that the actual resource usage of the self-built node is greater than the preset usage or the self-built node fails, the CDN device can perform the following operations: reduce the resource rating of the self-built node; and / or control the ability to access the self-built node to be in a closed state.

[0136] If it is detected that the actual resource usage of the self-built node is greater than the preset usage or the self-built node fails, indicating that the self-built node cannot be accessed, in this case, the CDN device sends the subdomain name of the non-self-built node to the server, so that the server generates a second access address based on the primary domain name (the first primary domain name or the second primary domain name) and the subdomain name, and sends the access address to the client, so that the client can obtain the required data by accessing the non-self-built node.

[0137] It should be noted that the specific implementation of each step in this embodiment can refer to the relevant description in the above S104.

[0138] Based on the above method embodiment, the present application provides a data access device, which will be described below in conjunction with the accompanying drawings.

[0139] See also Figure 8 , the figure shows a data access device in a content distribution network provided in an embodiment of the present application. The device 800 is applied to a client and can realize the functions of the client, specifically including: a processing unit 801, a sending unit 802 and a receiving unit 803.

[0140] Wherein, the processing unit 801 is used to obtain a data access request;

[0141] The sending unit 802 is configured to send the data access request to the server if it is determined that the data access request is a quality-insensitive request, wherein the data access request is used to request an access address of a self-built node corresponding to a content delivery network CDN;

[0142] The receiving unit 803 is used to receive the first access address sent by the server if the self-built node can be accessed, and obtain the data to be accessed according to the first access address, where the first access address is the access address of the target self-built node.

[0143] In some implementations, the first access address is generated by the subdomain name of the target self-built node obtained by the server from the CDN device according to the data access request.

[0144] In some embodiments, the process of determining that the data access request is a quality-insensitive request includes: if the data access request is used to request non-first frame data of a video, obtaining the amount of data stored in the video buffer for the video; if the data amount meets a preset condition, determining that the data access request is a quality-insensitive request.

[0145] In some embodiments, if the data volume satisfies a preset condition, determining that the data access request is a quality-insensitive request includes: if the data volume makes the difference between an actual value of a service quality indicator corresponding to the client when playing the video and a required value of the service quality indicator corresponding to the video less than or equal to a preset threshold, determining that the data access request is a quality-insensitive request.

[0146] In some implementations, the process of determining that the data access request is a quality-insensitive request includes: if the service corresponding to the data access request is not a video playback service, determining that the data access request is a quality-insensitive request.

[0147] In some embodiments, the receiving unit 803 is also used to receive a second access address sent by the server if the self-built node cannot be accessed, and obtain the data to be accessed according to the second access address, where the second access address is an access address of a non-self-built node.

[0148] In some implementations, the inability to access the self-built node includes one or more of the following situations:

[0149] The ability of the server and / or the CDN device to access the self-built node is disabled;

[0150] The redundant resources of the self-built node are insufficient to support the data access request.

[0151] See also Fig. 9 , which is a structural diagram of a data access device in a content distribution network provided by an embodiment of the present application, such as Fig. 9 As shown, the device 900 is applied to a server to implement the functions of the server, and includes: a receiving unit 901, a sending unit 902, and a processing unit 903.

[0152] The receiving unit 901 is used to receive a data access request sent by a client, where the data access request is used to request an access address of a self-built node;

[0153] A sending unit 902 is configured to send the data access request to the CDN device if the self-built node can be accessed, where the data access request includes a first primary domain name, where the first primary domain name is a primary domain name used to access the self-built node;

[0154] The receiving unit 901 is further configured to receive a subdomain name of a target self-built node sent by the CDN device;

[0155] A processing unit 903 is configured to generate a first access address based on the first primary domain name and the subdomain name;

[0156] The sending unit 902 is further configured to send the first access address to the client, so that the client obtains the data to be accessed based on the first access address.

[0157] In some implementations, the target self-built node is a self-built node with redundant resources, and the target self-built node is a self-built node determined by the CDN device from at least one self-built node according to the data access request and capable of allowing the data access request to access.

[0158] In some embodiments, the sending unit 902 is also used to send a second access address to the client if the self-built node cannot be accessed, so that the client obtains the data to be accessed according to the second access address, and the second access address is the address corresponding to the non-self-built node.

[0159] In some implementations, the receiving unit 901 is specifically configured to receive a subdomain name of a non-self-built node sent by the CDN device if the ability of the CDN device to access the self-built node is in a closed state or the redundant resources of the self-built node are insufficient to support the data access request;

[0160] The processing unit 903 is specifically configured to generate a second access address according to the first primary domain name and the subdomain name;

[0161] The sending unit 902 is specifically configured to send a second access address to the client.

[0162] In some implementations, if the ability of the server device to access the self-built node is in a disabled state, the data access request includes a second primary domain name, where the second primary domain name is a primary domain name used when accessing a non-self-built node;

[0163] The receiving unit 901 is specifically configured to receive a subdomain name of a non-self-built node sent by the CDN device;

[0164] The processing unit 903 is specifically configured to generate a second access address according to the second primary domain name and the subdomain name;

[0165] The sending unit 902 is specifically configured to send a second access address to the client.

[0166] See also Fig.10 , this figure is a structural diagram of a data access device in a content distribution network provided in an embodiment of the present application. The device 1000 is applied to a CDN device and can realize the functions of the CDN device, including: a receiving unit 1001, a processing unit 1002 and a sending unit 1003.

[0167] The receiving unit 1001 is used to receive a data access request sent by the server, wherein the data access request is used to request a subdomain name of a node to be accessed;

[0168] The processing unit 1002 is configured to determine a target self-built node from at least one self-built node according to the data access request if the self-built node can be accessed;

[0169] The sending unit 1003 is used to send the subdomain name corresponding to the target self-built node to the server, so that the server generates a first access address according to the primary domain name of the target self-built node and the subdomain name, and sends the first access address to the client.

[0170] In some embodiments, the processing unit 1002 is specifically used to determine at least one self-built node corresponding to the location information based on the location information in the data access request; and determine a self-built node with redundant resources as a target self-built node based on the resource rated quantity and actual resource usage corresponding to the self-built node.

[0171] In some implementations, the receiving unit 1001 is further configured to receive resource ratings and actual resource usage sent by a self-built node.

[0172] In some embodiments, the processing unit 1002 is also used to lower the rated amount of resources of the self-built node in response to detecting that the actual usage of resources of the self-built node is greater than a preset usage or that the self-built node fails; and / or, control the ability to access the self-built node to be in a closed state.

[0173] In some embodiments, the sending unit 1003 is also used to send a subdomain name of a non-self-built node to the server if the self-built node cannot be accessed, so that the server generates a second access address based on the main domain name and the subdomain name, and sends the second access address to the client.

[0174] It should be noted that the specific implementation of each unit in the above-mentioned device embodiments can refer to the relevant description in the above-mentioned method embodiments. The division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The functional units in the embodiments of the present application can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. For example, in the above-mentioned embodiments, the processing unit and the sending unit can be the same unit or different units. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0175] See also Fig.11 , which shows a schematic diagram of the structure of an electronic device 1100 suitable for implementing the embodiment of the present disclosure. The terminal device in the embodiment of the present disclosure may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig.11The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0176] like Fig.11 As shown, the electronic device 1100 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 1101, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1102 or a program loaded from a storage device 1108 to a random access memory (RAM) 1103. In the RAM 1103, various programs and data required for the operation of the electronic device 1100 are also stored. The processing device 1101, the ROM 1102, and the RAM 1103 are connected to each other via a bus 1104. An input / output (I / O) interface 1105 is also connected to the bus 1104.

[0177] Typically, the following devices may be connected to the I / O interface 1105: an input device 1106 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 1107 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 1108 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1109. The communication device 1109 may allow the electronic device 1100 to communicate with other devices wirelessly or by wire to exchange data. Although Fig.11 The electronic device 1100 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0178] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 1109, or installed from the storage device 1108, or installed from the ROM 1102. When the computer program is executed by the processing device 1101, the above-mentioned functions defined in the method of the embodiment of the present disclosure are executed.

[0179] The electronic device provided by the embodiment of the present disclosure and the method provided by the above embodiment belong to the same inventive concept, and the technical details not fully described in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0180] The embodiments of the present disclosure provide a computer storage medium on which a computer program is stored. When the program is executed by a processor, the method provided by the above embodiments is implemented.

[0181] It should be noted that the computer-readable medium disclosed above may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, device or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. This propagated data signal may take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0182] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (Hyper Text Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0183] The computer-readable medium may be included in the electronic device, or may exist independently without being incorporated into the electronic device.

[0184] The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device can execute the method.

[0185] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0186] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession 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 square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0187] The units involved in the embodiments described in the present disclosure may be implemented by software or hardware, wherein the name of a unit / module does not, in some cases, constitute a limitation on the unit itself.

[0188] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0189] It should be noted that the various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments, and the same or similar parts between the various embodiments can be referred to each other. For the system or device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part description.

[0190] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0191] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0192] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for accessing data in a content distribution network, characterized in that: The method is applied to a client and includes: Get data access request; If it is determined that the data access request is a quality-insensitive request, sending the data access request to the server, wherein the data access request is used to request an access address of a self-built node corresponding to a content delivery network CDN; If the self-built node can be accessed, a first access address sent by the server is received, and the data to be accessed is acquired according to the first access address, where the first access address is the access address of the target self-built node.

2. The method according to claim 1, characterized in that: The first access address is generated by the subdomain name of the target self-built node obtained by the server from the CDN device according to the data access request.

3. The method according to claim 1, characterized in that The process of determining that the data access request is a quality-insensitive request comprises: If the data access request is for requesting non-first frame data of a video, obtaining the amount of data stored in the video buffer for the video; If the data volume meets a preset condition, it is determined that the data access request is a quality-insensitive request.

4. The method according to claim 3, characterized in that If the data volume satisfies a preset condition, determining that the data access request is a quality-insensitive request includes: If the data volume makes the difference between the actual value of the service quality indicator corresponding to the client when playing the video and the required value of the service quality indicator corresponding to the video less than or equal to a preset threshold, the data access request is determined to be a quality-insensitive request.

5. The method according to claim 1, characterized in that The process of determining that the data access request is a quality-insensitive request comprises: If the service corresponding to the data access request is not a video playback service, it is determined that the data access request is a quality-insensitive request.

6. The method according to claim 1, characterized in that The method further comprises: If the self-built node cannot be accessed, a second access address sent by the server is received, and the data to be accessed is obtained according to the second access address, where the second access address is an access address of a non-self-built node.

7. The method according to claim 6, characterized in that The inability to access the self-built node includes one or more of the following situations: The ability of the server and / or the CDN device to access the self-built node is disabled; The redundant resources of the self-built node are insufficient to support the data access request.

8. A method for accessing data in a content distribution network, characterized in that: The method is applied to the server, and includes: Receive a data access request sent by a client, where the data access request is used to request an access address of a self-built node; If the self-built node can be accessed, the data access request is sent to the CDN device, where the data access request includes the first primary domain name, where the first primary domain name is the primary domain name used to access the self-built node; Receiving a subdomain name of a target self-built node sent by the CDN device, and generating a first access address based on the first primary domain name and the subdomain name; The first access address is sent to the client, so that the client obtains the data to be accessed based on the first access address.

9. The method according to claim 8, characterized in that The target self-built node is a self-built node with redundant resources, and the target self-built node is a self-built node determined by the CDN device from at least one self-built node according to the data access request and is allowed to be accessed by the data access request.

10. The method according to claim 8, characterized in that The method further comprises: If the self-built node cannot be accessed, a second access address is sent to the client, so that the client obtains the data to be accessed according to the second access address, and the second access address is an address corresponding to the non-self-built node.

11. The method according to claim 10, characterized in that If the self-built node cannot be accessed, sending a second access address to the client comprises: If the CDN device's ability to access the self-built node is in a disabled state or the redundant resources of the self-built node are insufficient to support the data access request, receiving the subdomain name of the non-self-built node sent by the CDN device; Generate a second access address according to the first primary domain name and the subdomain name; Sending a second access address to the client.

12. The method according to claim 10, characterized in that If the self-built node cannot be accessed, sending a second access address to the client comprises: If the ability of the server device to access the self-built node is in a disabled state, the data access request includes a second primary domain name, where the second primary domain name is a primary domain name used when accessing a non-self-built node; Receiving a subdomain name of a non-self-built node sent by the CDN device; Generate a second access address according to the second primary domain name and the subdomain name; Sending a second access address to the client.

13. A method for accessing data in a content distribution network, characterized in that: The method is applied to a CDN device, comprising: Receive a data access request sent by the server, where the data access request is used to request a subdomain name of a node to be accessed; If the self-built node can be accessed, the target self-built node is determined from at least one self-built node according to the data access request, and the subdomain name corresponding to the target self-built node is sent to the server, so that the server generates a first access address according to the primary domain name of the target self-built node and the subdomain name, and sends the first access address to the client.

14. The method according to claim 13, characterized in that The determining a target self-built node from at least one self-built node according to the data access request includes: Determine at least one self-built node corresponding to the location information according to the location information in the data access request; A self-built node with redundant resources is determined as a target self-built node according to the resource rating and actual resource usage corresponding to the self-built node.

15. The method according to claim 14, characterized in that The method further comprises: Receive the resource rating and actual resource usage sent by the self-built node.

16. The method according to claim 15, characterized in that In response to detecting that the actual resource usage of the self-built node is greater than a preset usage or the self-built node fails, the method further includes one or more of the following: Lowering the resource rating of the self-built node; The ability to control access to self-built nodes is disabled.

17. The method according to claim 13, characterized in that The method further comprises: If the self-built node cannot be accessed, the subdomain name of the non-self-built node is sent to the server, so that the server generates a second access address according to the main domain name and the subdomain name, and sends the second access address to the client.

18. A data access device in a content distribution network, characterized in that: The device is applied to a client and includes: A processing unit, configured to obtain a data access request; A sending unit, configured to send the data access request to a server if it is determined that the data access request is a quality-insensitive request, wherein the data access request is used to request an access address of a self-built node corresponding to a content delivery network CDN; The receiving unit is used to receive the first access address sent by the server if the self-built node can be accessed, and obtain the data to be accessed according to the first access address, where the first access address is the access address of the target self-built node.

19. A data access device in a content distribution network, characterized in that: The device is applied to a server, and includes: A receiving unit, used to receive a data access request sent by a client, wherein the data access request is used to request an access address of a self-built node; A sending unit, configured to send the data access request to the CDN device if the self-built node can be accessed, wherein the data access request includes a first primary domain name, and the first primary domain name is a primary domain name used to access the self-built node; The receiving unit is further configured to receive the subdomain name of the target self-built node sent by the CDN device; A processing unit, configured to generate a first access address using the first primary domain name and the subdomain name; The sending unit is further configured to send the first access address to the client, so that the client obtains the data to be accessed based on the first access address.

20. A data access device in a content distribution network, characterized in that: The device is applied to CDN equipment, including: A receiving unit, used to receive a data access request sent by a server, wherein the data access request is used to request a subdomain name of a node to be accessed; a processing unit, configured to determine a target self-built node from at least one self-built node according to the data access request if the self-built node can be accessed; The sending unit is used to send the subdomain name corresponding to the target self-built node to the server, so that the server generates a first access address according to the primary domain name of the target self-built node and the subdomain name, and sends the first access address to the client.

21. An electronic device, characterized in that: The device comprises: a processor and a memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs in the memory so that the electronic device executes the method according to any one of claims 1 to 17.

22. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, and when the instructions are executed on a device, the device executes the method according to any one of claims 1 to 17.

Citation Information

Patent Citations

  • Content distribution network routing method, system, and user terminal

    CN102668518A

  • Video CDN scheduling optimization method and device

    CN107948004A

  • Access request processing method and device and electronic equipment

    CN112153160A

  • CDN-based communication method, system and device, and storage medium

    CN114301848A

  • Download prioritization for intelligent content distribution

    US8036690B1