CN110839049A

CN110839049A - Data scheduling method and system based on domain name system

Info

Publication number: CN110839049A
Application number: CN201810931364.XA
Authority: CN
Inventors: 王维; 任海
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2018-08-15
Filing date: 2018-08-15
Publication date: 2020-02-25
Anticipated expiration: 2038-08-15
Also published as: CN110839049B

Abstract

The application discloses a data scheduling method and system based on a domain name system. Wherein, the method comprises the following steps: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network. The method and the device solve the technical problem that in the process of playing the video in the prior art, the playing request is scattered to a plurality of CDN nodes, so that the hit rate is low.

Description

Data scheduling method and system based on domain name system

Technical Field

The present application relates to the field of data scheduling, and in particular, to a data scheduling method and system based on a domain name system.

Background

The acceleration of existing commercial CDNs (Content Delivery networks) is basically based on domain name. Most of the scheduling of users and traffic is based on DNS basically, and the specific principle is as shown in fig. 1, where a user accesses a live URL: http:// host.com/app/team.flv live content; the operator's recursive Forward DNS removes the root (·) authoritative DNS queries.ns (Name Server) records for com., the root () returns NS for com. The forwarding DNS of the operator goes to com.authoritative DNS to inquire the NS record of host.com.; the forwarding DNS of the operator goes to a host authority DNS to inquire an A record of host.com. the host authority returns the A (1.1.1.1) record to the forwarding DNS of the operator; the forwarding DNS of the operator returns the a record to the user. In the CDN scheduling system, the host authority is the CDN scheduling system, and the host returns the IP address of the nearest CDN node according to the IP attribution condition of a Forward DNS.

However, the granularity of address judgment based on the DNS is coarse, and the DNS may be far from the network of the user, and the user may also set an incorrect DNS, which is far from the actual distance of the server and the user; the DNS request does not carry content information, and more flexible judgment can not be made for the content; because the DNS has TTL (Time To Live) cache, a request of a user within a period of Time is directed To the same CDN node, which may cause that when the node traffic is high, the traffic cannot be cut away, and user experience is affected; due to the problems existing in scheduling, service experience data are affected, and specifically, the card pause rate is affected due to scheduling inaccuracy; content-based scheduling cannot be used to affect hit rates, and therefore, first screen and stuck rates.

The resolution of the Domain Name of a part of CPs (Content Provider) is basically realized based on HTTP DNS (Hyper Text Transfer Protocol Domain Name System, hypertext Transfer Protocol Domain Name server), and the specific principle is as shown in fig. 2, after a player of a user acquires a play url (uniform Resource locator), the player requests an HTTP DNS interface to obtain a record information of the Domain Name of the player; after the HTTP DNS obtains a request from a user, the user ip (client ip) is identified according to a Domain name (Domain); the IP of the node to select the CDN is returned to the user.

However, the HTTP DNS request does not carry content information, and thus a more flexible determination cannot be made for the content; the problem of centralized deployment of the HTTP DNS can seriously affect the usability of the service; because the problem of scheduling can lead to that the business experience data is very influenced, the scheduling that can not be based on the content can influence the hit rate, and then influences the first screen and the pause rate.

Aiming at the problem of low hit rate caused by the fact that playing requests are scattered to a plurality of CDN nodes in the process of playing videos in the prior art, an effective solution is not provided at present.

Disclosure of Invention

The embodiment of the application provides a data scheduling method and system based on a domain name system, which are used for at least solving the technical problem of low hit rate caused by the fact that playing requests are scattered to a plurality of CDN nodes in the process of playing videos in the prior art.

According to an aspect of an embodiment of the present application, a data scheduling method based on a domain name system is provided, including: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

According to another aspect of the embodiments of the present application, there is also provided a data scheduling method based on a domain name system, including: the method comprises the steps that an edge server receives a content request sent by a client terminal, wherein the client terminal finishes domain name scheduling in a content distribution network to obtain address information of the edge server in the content distribution network; if the edge server caches the data requested by the content request locally, the edge server sends the data corresponding to the content request to the client terminal, wherein the content request at least comprises the following steps: domain name, address information of client terminal; if the edge server does not cache the data requested by the content request locally, the edge server acquires the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

According to another aspect of the embodiments of the present application, there is also provided a data scheduling system based on a domain name system, including: the client terminal is used for completing domain name scheduling in the content distribution network, obtaining address information of an edge server in the content distribution network, and sending a content request based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; the edge server is used for receiving and responding to the content request and returning the data obtained by the request to the client terminal; the scheduling center is used for receiving the content request sent by the edge server if the edge server does not locally cache the data requested by the content request, and determining the optimal access node in the network area where the client terminal is located based on the content request; the edge server obtains the data requested by the content request by accessing the optimal access node.

According to another aspect of the embodiments of the present application, there is also provided a data scheduling system based on a domain name system, including: the client terminal is used for completing domain name scheduling in the content distribution network, obtaining address information of an edge server in the content distribution network, and sending a content request based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; the edge server is used for receiving the content request and judging whether the content request is flow granularity scheduling or not; the edge scheduler is used for receiving the content request after the edge server judges that the content request is not the stream granularity scheduling; the scheduling center is used for receiving the content request sent by the edge scheduler and determining the optimal access node in the network area where the client terminal is located based on the content request if the edge scheduler does not locally cache the data requested by the content request; the edge server obtains the data requested by the content request by accessing the optimal access node.

According to another aspect of the embodiments of the present application, there is also provided a storage medium including a stored program, where the program, when executed, controls an apparatus on which the storage medium is located to perform the following steps: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

According to another aspect of the embodiments of the present application, there is also provided a mobile device, including: a processor for executing the program, wherein the following steps are performed when the program is executed: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

According to another aspect of the embodiments of the present application, there is also provided a data scheduling system based on a domain name system, including: a processor; and a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

In the embodiment of the application, the client terminal completes domain name scheduling in the content distribution network, can obtain address information of an edge server in the content distribution network, sends a content request to the edge server based on the address information, and receives data returned by the edge server in response to the content request, wherein the data can be data locally cached by the edge server or data requested by the edge server from a scheduling center, so that the purpose of domain name-based data scheduling is achieved.

It is easy to notice that after completing domain name scheduling, the client terminal obtains the address information of the edge server in the content distribution network, and the edge server responds to the content request to return data.

Therefore, the technical problem of low hit rate caused by the fact that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art is solved by the scheme provided by the embodiment of the application.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

FIG. 1 is a schematic diagram of a DNS based data scheduling method according to the prior art;

FIG. 2 is a schematic diagram of a HTTP DNS based data scheduling method according to the prior art;

fig. 3 is a block diagram of a hardware structure of a computer terminal (or a mobile device) for implementing a domain name system-based data scheduling method according to an embodiment of the present application;

fig. 4 is an exemplary block diagram of a computer terminal as a client terminal for implementing a domain name system-based data scheduling method according to an embodiment of the present application;

fig. 5 is a flowchart of a data scheduling method based on a domain name system according to embodiment 1 of the present application;

FIG. 6 is an interaction diagram of an alternative HTTP DNS based data scheduling method according to an embodiment of the present application;

FIG. 7 is an interaction diagram of an alternative DNS based data scheduling method according to an embodiment of the present application;

fig. 8 is a flowchart of a data scheduling method based on a domain name system according to embodiment 2 of the present application;

fig. 9 is a schematic diagram of a data scheduling apparatus based on a domain name system according to embodiment 3 of the present application;

fig. 10 is a schematic diagram of a data scheduling apparatus based on a domain name system according to embodiment 4 of the present application;

fig. 11 is a schematic diagram of a data scheduling system based on a domain name system according to embodiment 5 of the present application;

fig. 12 is a schematic diagram of a data scheduling system based on a domain name system according to embodiment 6 of the present application; and

fig. 13 is a block diagram of a computer terminal according to an embodiment of the present application.

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only partial embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

First, some terms or terms appearing in the description of the embodiments of the present application are applicable to the following explanations:

CDN: the basic idea of the content distribution network is to avoid bottlenecks and links on the internet which may affect the data transmission speed and stability as much as possible, so that the content transmission is faster and more stable. By placing node servers at various positions of the network to form a layer of intelligent virtual network on the basis of the existing internet, the CDN system can redirect the request of a user to a service node closest to the user in real time according to network flow, connection of each node, load condition, distance to the user, response time and other comprehensive information.

An edge server: the user may be provided with a channel to the network and the functionality to communicate with other server devices, typically a group of servers that perform a single function, such as DNS servers.

Example 1

According to an embodiment of the present application, there is provided an embodiment of a data scheduling method based on a domain name system, it should be noted that the steps shown in the flowchart of the drawings may be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in an order different from that here.

The method provided by the first embodiment of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Fig. 3 shows a block diagram of a hardware structure of a computer terminal (or mobile device) for implementing a domain name system-based data scheduling method. As shown in fig. 3, the computer terminal 10 (or mobile device 10) may include one or more (shown as 302a, 302b, … …, 302 n) processors 302 (the processors 302 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), memories 304 for storing data, and a transmission device 306 for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 3 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 3, or have a different configuration than shown in FIG. 3.

It should be noted that the one or more processors 302 and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuit may be a single stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computer terminal 10 (or mobile device). Such as the client terminal, edge server, referred to in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistance termination path to interface with).

The memory 304 may be used to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the data scheduling method based on the domain name system in the embodiment of the present application, and the processor 302 executes various functional applications and data processing by running the software programs and modules stored in the memory 304, that is, implementing the data scheduling method based on the domain name system. The memory 304 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 304 may further include memory located remotely from the processor 302, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 306 is used for receiving or sending data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission device 306 includes a Network Interface Controller (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device 306 can be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the computer terminal 10 (or mobile device).

Fig. 3 shows a block diagram of a hardware structure, which may be taken as an exemplary block diagram of not only the computer terminal 10 (or the mobile device) but also the server, and in an alternative embodiment, fig. 4 shows an embodiment of using the computer terminal 10 (or the mobile device) shown in fig. 3 as a client terminal in a block diagram. As shown in fig. 4, the computer terminal 10 (or mobile device) may be connected or electronically connected via a data network connection to one or more servers 00, e.g., DNS servers, edge servers, etc. In an alternative embodiment, the computer terminal 10 (or mobile device) may be any mobile computing device or the like. The data network connection may be a local area network connection, a wide area network connection, an internet connection, or other type of data network connection. The computer terminal 10 (or mobile device) may execute to connect to a network service executed by a server (e.g., a secure server) or a group of servers. A web server is a network-based user service such as social networking, cloud resources, email, online payment, or other online applications.

Under the operating environment, the application provides a data scheduling method based on a domain name system as shown in fig. 5.

Fig. 5 is a flowchart of a data scheduling method based on a domain name system according to embodiment 1 of the present application. As shown in fig. 5, the method may include the steps of:

in step S52, the client terminal obtains address information of the edge server in the content distribution network by completing domain name scheduling in the content distribution network.

Specifically, the client terminal may be a mobile device or a computer device used by a user, including but not limited to: smart phones (including Android and IOS phones), IPADs, tablet computers, palm top computers, notebook computers, PCs (Personal computers), and the like.

In an optional scheme, the client terminal may obtain the IP of the edge server of the CDN by completing DNS scheduling in the CDN.

Step S54, the client terminal sends a content request to the edge server based on the address information, wherein the content request at least includes: domain name, address information of the client terminal.

Specifically, the address information of the client terminal may be an IP of the client terminal. In the content request, the domain name may be represented by a domain parameter, and the IP of the client terminal may be represented by a client _ IP parameter. In order to facilitate the edge server to determine whether corresponding data is cached locally, the content request may further include: a data stream can be represented by a stream parameter in a content request.

In an alternative scheme, the client terminal may send a content request carrying domain, stream, and client _ ip parameters to the edge server.

In step S56, if the edge server caches the data requested by the content request locally, the client terminal will receive the data directly returned by the edge server.

In step S58, if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

In an optional scheme, after receiving a content request sent by a client terminal, an edge server may determine whether corresponding data is locally cached based on a stream and a client _ ip, and if the corresponding data is locally cached, the edge server may return the locally cached corresponding data to the client terminal, and if the corresponding data is not locally cached by the edge server, the edge server may request a scheduling center in the CDN for responsive data, and obtain the corresponding data from the scheduling center of the CDN and return the corresponding data to the client terminal.

In another optional scheme, after receiving a content request sent by a client terminal, an edge server may return corresponding data cached locally to the client terminal, or send the content request to an edge scheduler to obtain the corresponding data cached locally by the edge scheduler, and if the edge scheduler does not cache the corresponding data, may request a scheduling center in the CDN for responsive data, obtain the corresponding data from the scheduling center of the CDN, and return the corresponding data to the client terminal.

In the solution provided by the foregoing embodiment 1 of the present application, a client terminal completes domain name scheduling in a content distribution network, may obtain address information of an edge server in the content distribution network, sends a content request to the edge server based on the address information, and receives data returned by the edge server in response to the content request, where the data may be data locally cached by the edge server or data requested by the edge server from a scheduling center, so as to achieve a purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 1 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

In the above embodiment of the present application, in step S58, the requesting, by the edge server, data by accessing the dispatch center of the content distribution network includes:

in step S582, the scheduling center receives the content request sent by the edge server.

Step S584, the scheduling center determines the network area where the client terminal is located according to the address information of the client terminal.

Step S586, the scheduling center determines the optimal access node in the network region according to the domain name and the data flow.

Specifically, the scheduling center can select an optimal CDN node as an optimal access node in operator nodes of an area ISP through a stream-based consistent hash algorithm.

In step S588, the scheduling center returns the address information of the optimal access node to the edge server, so that the edge server obtains the data requested by the content request by accessing the optimal access node.

In an optional scheme, for domain name resolution implemented based on HTTP DNS, after receiving a content request sent by an edge server, a scheduling center may select an Internet Service Provider (ISP) to which a user belongs according to a client _ ip carried in the content request, then confirm a specific CDN node in the ISP as an optimal access node according to domain and stream, and return address information of the optimal access node to the edge server, so that the edge server may obtain corresponding data from the optimal access node and return the data to a client terminal.

In the above embodiments of the present application, the edge server returns the data requested from the optimal access node to the client terminal, and locally caches the data requested by the content request.

In an optional scheme, for domain name resolution implemented based on the HTTP DNS, after receiving address information of an optimal access node returned by a scheduling center, an edge server may obtain corresponding data from the optimal access node and return the data to a client terminal, and simultaneously locally cache the corresponding data, so that when the client terminal sends the same content request next time, the edge server may directly return the corresponding data to the client terminal, thereby further achieving the effects of improving a hit rate, improving interface availability, and reducing a first screen time and a pause rate.

Fig. 6 is an interaction diagram of an alternative HTTP DNS-based data scheduling method according to an embodiment of the present application, and as shown in fig. 6, the method may include the following steps:

in step S61, the client terminal requests the HTTP DNS interface to transmit a content request carrying the domain, stream, and client _ ip parameters.

Alternatively, the content request sent by the client terminal may be a URL, for example, the content request may be http:// api. httpdns. com/stream ab & client _ ip ═ 1.1.1.1& domain ab.com.

In step S62, the HTTP DNS edge node determines whether the information requested by the user is cached locally.

In step S63, if the HTTP DNS edge node has a cache locally, corresponding data is returned.

Alternatively, the HTTP DNS edge node may return CDN node a record information to the client terminal.

Step S64, if the HTTP DNS edge node is not cached locally, a content request carrying the parameters of domain, stream and client _ ip is sent to the HTTP DNS center node.

Alternatively, the HTTP DNS edge node may request a record information of the CDN node from the HTTP DNS hub node.

And step S65, the HTTP DNS central node selects the optimal node of the CDN according to the domain, the stream and the client _ ip.

Optionally, the HTTP DNS central node selects an area ISP to which the user belongs according to the client _ ip, and then confirms a specific CDN node in the area ISP according to domain and stream to obtain an optimal node.

Step S66, the HTTP DNS central node returns the optimal node to the HTTP DNS edge node, and the HTTP DNS edge node obtains corresponding data from the optimal node and caches the data.

Optionally, after receiving the information returned by the HTTP DNS central node, the HTTP DNS edge node may obtain the a record information of the CDN node from the optimal node, and cache the information according to the stream and the client _ ip.

At step S67, the HTTP DNS edge node returns corresponding data to the client terminal.

By the scheme, the scheduling method of the service layer is added on the basis of the scheduling of the HTTP DNS, so that the quality of the live broadcast service can be improved, and the cost of the live broadcast service is reduced. By sinking the HTTP DNS to the edge node of the CDN, the HTTP DNS has the same distributed deployment as the CDN, the failure condition of user request is greatly reduced, and the high availability of the interface is effectively improved; the HTTP DNS can be based on the scheduling of stream granularity, so that the hit rate of the stream at the edge node can be greatly improved, and the first screen time, the pause rate and the downlink bandwidth of the CDN center node can be effectively reduced.

In the foregoing embodiment of the present application, in step S54, after the client terminal sends the content request to the edge server based on the address information, the method further includes:

in step S510, the edge server determines whether the content request is a request after stream granularity scheduling.

Step S512, if yes, the edge server responds to the content request and returns the response result to the client terminal.

If not, the edge server requests the scheduling policy of the flow granularity from the edge scheduler in step S514.

In an optional scheme, for domain name resolution implemented based on DNS, after receiving a content request URL, an edge server may determine whether the URL is a URL after stream granularity scheduling, and if so, return corresponding content; if not, a scheduling policy at the flow granularity is requested from the edge scheduler.

In the above embodiment of the present application, after the step S514, the edge server requests the edge scheduler for the scheduling policy of the flow granularity, the method further includes:

in step S518, the edge scheduler receives the content request.

In step S520, the edge scheduler inquires whether the data requested by the content request is cached locally.

In step S522, if the edge scheduler locally caches the data requested by the content request, the edge scheduler returns the data to the client terminal through the edge server.

In an alternative, for DNS-based domain name resolution, the edge scheduler, after receiving the content request, by determining that the message: and the stream and the client _ ip are used for inquiring whether the same analysis record exists in the local cache or not, if so, the corresponding data is determined to be cached locally, the corresponding data is returned to the edge server, and the edge server forwards the corresponding data to the client terminal.

In the above embodiment of the present application, in step S524, if the edge scheduler does not locally cache the data requested by the content request, the edge scheduler obtains the data requested by the content request by accessing the scheduling center of the content distribution network, and returns the data to the client terminal.

In an optional scheme, for domain name resolution implemented based on the DNS, if the edge scheduler queries that there is no same resolution record in the local cache, it is determined that corresponding data is not locally cached, an optimal access node may be requested from the scheduling center, and corresponding data is acquired from the optimal access node.

In the above embodiment of the present application, in step S524, the obtaining, by the edge scheduler, data requested by the content request by accessing the scheduling center of the content distribution network includes:

in step S5242, the scheduling center receives the content request sent by the edge scheduler.

In step S5244, the scheduling center determines the network area where the client terminal is located according to the address information of the client terminal.

Step S5246, the scheduling center determines an optimal access node in the network area according to the domain name and the data stream.

In step S5248, the scheduling center returns the address information of the optimal access node to the edge scheduler, so that the edge scheduler obtains the data requested by the content request by accessing the optimal access node.

In an optional scheme, for domain name resolution implemented based on DNS, after receiving a content request sent by an edge scheduler, a scheduling center may select an ISP home location of a user according to a client _ ip carried in the content request, then select a specific CDN node as an optimal access node from operator nodes to which the ISP home location is according to domain and stream, and return address information of the optimal access node to the edge scheduler, so that the edge scheduler may obtain corresponding data from the optimal access node and return the data to a client terminal through an edge server.

In the above embodiment of the present application, in step S526, after receiving the address information of the optimal access node returned by the scheduling center, the edge scheduler sends the address information of the optimal access node to the edge server, and locally caches an analysis result, where the analysis result is that the edge server obtains data requested by the content request by accessing the optimal access node.

In an optional scheme, for domain name resolution implemented based on DNS, after receiving address information of an optimal access node returned by a scheduling center, an edge scheduler may forward the address information of the optimal access node to an edge server, and the edge server may obtain corresponding data from the optimal access node and return the data to the edge scheduler, and the edge scheduler performs local cache, so that when the client terminal sends the same content request next time, the edge scheduler may directly return the corresponding data to the client terminal, thereby further achieving the effects of improving a hit rate, improving interface availability, and reducing first screen time and a pause rate.

In the above embodiment of the present application, in step S526, after the edge server obtains the data requested by the content request by accessing the optimal access node, the method further includes:

in step S528, the edge server sends the data to the client terminal, and locally caches the requested data.

In an optional scheme, for domain name resolution implemented based on the DNS, after receiving address information of an optimal access node returned by a scheduling center, an edge server may obtain corresponding data from the optimal access node and return the data to a client terminal, and simultaneously locally cache the corresponding data, so that when the client terminal sends the same content request next time, the edge server may directly return the corresponding data to the client terminal, thereby further achieving the effects of improving a hit rate, improving interface availability, and reducing a first screen time and a pause rate.

in step S530, the edge server sends address jump information to the client terminal, where the address jump information causes the web page on the client terminal to jump to the web page of the requested data.

In an alternative scheme, for domain name resolution implemented based on DNS, the edge server may return address jump information to the client terminal, so that a web page on the client terminal may jump to a web page of corresponding data.

Fig. 7 is an interaction diagram of an alternative DNS-based data scheduling method according to an embodiment of the present application, and as shown in fig. 7, the method may include the following steps:

step S71, after completing DNS scheduling, the client terminal acquires an edge node IP of the CDN, and requests content from the CDN edge node.

Optionally, the content request sent by the client terminal may be a URL, for example, the content request may be http:// host.com/app/stream.flv, and the parameter carried in the content request is not written out.

In step S72, the CDN edge node determines whether the URL requested by the user is a URL after stream granularity scheduling.

In step S73, if the URL requested by the user is a URL after stream granularity scheduling, corresponding data is returned.

Optionally, the CDN edge node may return live content.

Step S74, if the URL requested by the user is not the URL after the stream granularity scheduling, request a scheduling policy of the stream granularity from the CDN edge scheduler.

In step S75, the CDN edge scheduler determines whether the local cache has the same analysis record.

Optionally, the CDN edge scheduler may query whether there is the same parse record in the local cache according to the stream and the client _ ip.

In step S76, if the same analysis record is cached locally, the result is returned.

Optionally, if the CDN edge scheduler locally caches the same parsing record, corresponding data may be returned through the CDN edge node.

Step S77, if the same analysis record is not cached locally, an optimal CDN node is requested from the CDN scheduling center.

And step S78, the CDN scheduling center selects the optimal node of the CDN according to domain, stream and client _ ip.

Optionally, the HTTP DNS central node confirms the ISP attribution of the user according to the client _ ip, and then selects an optimal CDN node from the operator nodes to which the ISP belongs by using stream to perform consistent hash.

Step S79, the CDN scheduling center returns the optimal node to the CDN edge scheduler.

Step S710, the CDN edge scheduler returns the optimal node to the CDN edge node, and stores the analysis result at the same time.

Step S711, the CDN edge node returns the address jump information of the user 302 to the client terminal.

Alternatively, the address jump information may be: http:// cdn _ ip/domain/app/stream. flv.

By the scheme, the service layer and the user IP scheduling method are added on the basis of the DNS scheduling, so that the quality of the live broadcast service can be improved, and the cost of the live broadcast service is reduced. The CDN can acquire the client _ ip of the user to perform secondary scheduling, so that scheduling errors caused by DNS setting errors can be effectively avoided, and the problem that services after node traffic is out of date cannot be scheduled in time can also be avoided; the high availability of the interface can be effectively improved by sinking the scheduler to the edge node of the CDN; the CDN can be based on stream granularity scheduling, so that the hit rate of the stream at the edge node can be greatly improved, and the first-screen time, the pause rate and the downstream bandwidth of the CDN center node can be effectively reduced.

It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

Example 2

There is also provided, in accordance with an embodiment of the present application, an embodiment of a domain name system-based data scheduling method, it should be noted that the steps illustrated in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer-executable instructions, and that, although a logical order is illustrated in the flowchart, in some cases, the steps illustrated or described may be performed in an order different than here.

In the operating environment of the above embodiment 1, the present application provides a data scheduling method based on the domain name system as shown in fig. 8. Fig. 8 is a flowchart of a data scheduling method based on a domain name system according to embodiment 2 of the present application. As shown in fig. 8, the method may include the steps of:

in step S82, the edge server receives the content request sent by the client terminal, where the client terminal obtains the address information of the edge server in the content distribution network by completing domain name scheduling in the content distribution network.

In an optional scheme, the client terminal may obtain an IP of an edge server of the CDN by completing DNS scheduling in the CDN, and send a content request to the edge server.

Step S84, if the edge server caches the data requested by the content request locally, the edge server sends the data corresponding to the content request to the client terminal, where the content request at least includes: domain name, address information of the client terminal.

Step S86, if the edge server does not locally cache the data requested by the content request, the edge server obtains the data requested by the content request by accessing the scheduling center of the content distribution network, and returns the data to the client terminal.

In an optional scheme, after receiving a content request sent by a client terminal, an edge server determines whether corresponding data is locally cached based on stream and client _ ip, if the corresponding data is locally cached, the edge server may return the locally cached corresponding data to the client terminal, and if the corresponding data is not locally cached by the edge server, the edge server may request a scheduling center in the CDN for responsive data, obtain the corresponding data from the scheduling center of the CDN, and return the corresponding data to the client terminal.

In another optional scheme, after receiving a content request sent by a client terminal, an edge server may return corresponding data cached locally to the client terminal, or send a request to an edge scheduler to obtain the corresponding data cached locally by the edge scheduler, and if the edge scheduler does not cache the corresponding data, may request a scheduling center in the CDN for responsive data, obtain the corresponding data from the scheduling center of the CDN, and return the corresponding data to the client terminal.

According to the scheme provided by the embodiment 2 of the present application, a client terminal completes domain name scheduling in a content distribution network, and can obtain address information of an edge server in the content distribution network, the edge server receives a content request sent by the client terminal, if data requested by the content request is locally cached, the edge server directly sends data corresponding to the content request to the client terminal, and if the data requested by the content request is not locally cached, the edge server obtains the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal, thereby achieving the purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 2 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

In the foregoing embodiment of the present application, after the edge server receives the content request sent by the client terminal in step S82, the method further includes:

in step S88, the edge server determines whether the content request is a request after stream granularity scheduling.

Step S810, if yes, the edge server responds to the content request and returns the response result to the client terminal.

If not, the edge server requests the scheduling policy of the flow granularity from the edge scheduler, step S812.

Optionally, the requesting, by the edge server, data by accessing a scheduling center of the content distribution network includes: the method comprises the steps that a scheduling center receives a content request sent by an edge server; the dispatching center determines the network area where the client terminal is located according to the address information of the client terminal; the scheduling center determines an optimal access node in the network area according to the domain name and the data stream; and the dispatching center returns the address information of the optimal access node to the edge server, so that the edge server acquires the data requested by the content request by accessing the optimal access node.

Optionally, the edge server returns the data requested from the optimal access node to the client terminal, and locally caches the data requested by the content request.

Optionally, after the edge server requests the scheduling policy of the flow granularity from the edge scheduler, the method further includes: the edge scheduler receives a content request; the edge scheduler inquires whether the data requested by the content request is cached locally; if the edge scheduler has cached the data requested by the content request locally, the edge scheduler returns the data to the client terminal through the edge server.

Alternatively, if the edge scheduler does not locally cache the data requested by the content request, the edge scheduler obtains the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

Optionally, the obtaining, by the edge scheduler, data requested by the content request by accessing a scheduling center of the content distribution network includes: the scheduling center receives a content request sent by the edge scheduler; the dispatching center determines the network area where the client terminal is located according to the address information of the client terminal; the scheduling center determines an optimal access node in the network area according to the domain name and the data stream; the dispatching center returns the address information of the optimal access node to the edge dispatcher, so that the edge dispatcher acquires the data requested by the content request by accessing the optimal access node.

Optionally, after receiving the address information of the optimal access node returned by the scheduling center, the edge scheduler sends the address information of the optimal access node to the edge server, and locally caches an analysis result, where the analysis result is that the edge server obtains data requested by the content request by accessing the optimal access node.

Optionally, after the edge server obtains the data requested by the content request by accessing the optimal access node, the method further includes: the edge server sends the data to the client terminal and locally caches the requested data for content requests.

Optionally, after the edge server obtains the data requested by the content request by accessing the optimal access node, the method further includes: the edge server sends address hopping information to the client terminal, wherein the address hopping information causes the web page on the client terminal to hop to the web page of the requested data.

Example 3

According to an embodiment of the present application, there is also provided a data scheduling apparatus based on a domain name system, for implementing the data scheduling method based on the domain name system, as shown in fig. 9, the apparatus 900 includes: an obtaining module 902, a sending module 904 and a receiving module 906.

The obtaining module 902 is configured to obtain address information of an edge server in a content distribution network by completing domain name scheduling in the content distribution network; the sending module 904 is configured to send a content request to the edge server based on the address information, where the content request at least includes: domain name, address information of client terminal; the receiving module 906 is configured to receive data directly returned by the edge server if the edge server locally caches data requested by the content request, and receive data requested by the edge server through a scheduling center accessing the content distribution network if the edge server does not locally cache data requested by the content request.

Specifically, the client terminal may be a mobile device or a computer device used by a user, including but not limited to: smart phones (including Android and IOS phones), IPADs, tablet computers, palm top computers, notebook computers, PCs (Personal computers), and the like. The address information of the client terminal may be an IP of the client terminal. In the content request, the domain name may be represented by a domain parameter, and the IP of the client terminal may be represented by a client _ IP parameter. In order to facilitate the edge server to determine whether corresponding data is cached locally, the content request may further include: a data stream can be represented by a stream parameter in a content request.

It should be noted here that the acquiring module 902, the sending module 904 and the receiving module 906 correspond to steps S52 to S58 in embodiment 1, and the three modules are the same as the corresponding steps in the implementation example and application scenario, but are not limited to the disclosure in embodiment 1. It should be noted that the above modules may be operated in the computer terminal 10 provided in embodiment 1 as a part of the apparatus.

In the solution provided by the foregoing embodiment 3 of the present application, the client terminal completes domain name scheduling in the content distribution network through the obtaining module, may obtain address information of an edge server in the content distribution network, sends a content request to the edge server based on the address information through the sending module, and receives data returned by the edge server in response to the content request through the receiving module, where the data may be data locally cached by the edge server, or data requested by the edge server from a scheduling center, so as to achieve a purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 3 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

Example 4

According to an embodiment of the present application, there is also provided a data scheduling apparatus based on a domain name system, for implementing the data scheduling method based on the domain name system, as shown in fig. 10, the apparatus 1000 includes: a receiving module 1002 and a transmitting module 1004.

The receiving module 1002 is configured to receive a content request sent by a client terminal, where the client terminal obtains address information of an edge server in a content distribution network by completing domain name scheduling in the content distribution network; the sending module 1004 is configured to send data corresponding to the content request to the client terminal if the edge server caches the data requested by the content request locally, and obtain the data requested by the content request by accessing a scheduling center of the content distribution network and return the data to the client terminal if the edge server does not cache the data requested by the content request locally.

It should be noted here that the receiving module 1002 and the sending module 1004 correspond to steps S82 to S86 in embodiment 2, and the two modules are the same as the corresponding steps in the implementation example and application scenario, but are not limited to the disclosure in embodiment 2. It should be noted that the above modules may be operated in the computer terminal 10 provided in embodiment 1 as a part of the apparatus.

According to the scheme provided by the foregoing embodiment 4 of the present application, a client terminal completes domain name scheduling in a content distribution network, and may obtain address information of an edge server in the content distribution network, where the edge server receives a content request sent by the client terminal through a receiving module, and if data requested by the content request is locally cached, the edge server directly sends data corresponding to the content request to the client terminal, and if the data requested by the content request is not locally cached, the edge server obtains the data requested by the content request by accessing a scheduling center of the content distribution network, and returns the data to the client terminal, thereby achieving the purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 4 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

Example 5

According to an embodiment of the present application, an embodiment of a data scheduling system based on a domain name system is provided, as shown in fig. 11, the system includes: a client terminal 10, an edge server 20 and a dispatch center 30.

The client terminal 10 is configured to obtain address information of an edge server 20 in a content distribution network by completing domain name scheduling in the content distribution network, and send a content request based on the address information, where the content request at least includes: domain name, address information of client terminal; the edge server is used for receiving and responding to the content request and returning the data obtained by the request to the client terminal; the dispatching center 30 is used for receiving the content request sent by the edge server if the edge server does not locally cache the data requested by the content request, and determining the optimal access node in the network area where the client terminal is located based on the content request; the edge server obtains the data requested by the content request by accessing the optimal access node.

According to the scheme provided by the embodiment 5 of the present application, a client terminal completes domain name scheduling in a content distribution network, so as to obtain address information of an edge server in the content distribution network, send a content request to the edge server based on the address information, and receive data returned by the edge server in response to the content request, if the edge server does not locally cache the data requested by the content request, a scheduling center receives the content request sent by the edge server, and determines an optimal access node in a network area where the client terminal is located based on the content request, and the edge server obtains the data requested by the content request by accessing the optimal access node and returns the data to the client terminal, thereby achieving the purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 5 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

Optionally, the edge server is further configured to return the requested data to the client terminal if the data requested by the content request is cached locally.

Optionally, the scheduling center is further configured to receive a content request sent by the edge server, determine a network area where the client terminal is located according to address information of the client terminal, determine an optimal access node in the network area according to a domain name and a data stream, and return address information of the optimal access node to the edge server, so that the edge server obtains data requested by the content request by accessing the optimal access node.

Optionally, the edge server is further configured to return the data acquired from the optimal access node to the client terminal, and locally cache the data requested by the content request.

Example 6

According to an embodiment of the present application, an embodiment of a data scheduling system based on a domain name system is provided, as shown in fig. 12, the system includes: client terminal 10, edge server 20, dispatch center 30, and edge scheduler 40.

The client terminal 10 is configured to obtain address information of an edge server 20 in a content distribution network by completing domain name scheduling in the content distribution network, and send a content request based on the address information, where the content request at least includes: domain name, address information of client terminal; the edge server is used for receiving the content request and judging whether the content request is flow granularity scheduling or not; the edge scheduler 40 is configured to receive the content request after the edge server determines that the content request is not a stream granularity schedule; the scheduling center 30 is configured to receive the content request sent by the edge scheduler if the edge scheduler does not locally cache the data requested by the content request, and determine an optimal access node in the network area where the client terminal is located based on the content request; the edge server obtains the data requested by the content request by accessing the optimal access node.

In the solution provided by the foregoing embodiment 6 of the present application, a client terminal completes domain name scheduling in a content distribution network, so as to obtain address information of an edge server in the content distribution network, send a content request to the edge server based on the address information, the edge server determines whether the content request is stream granularity scheduling, after the edge server determines that the content request is not stream granularity scheduling, the edge scheduler receives the content request, if the edge scheduler does not locally cache data requested by the content request, receives the content request sent by the edge scheduler, and determines an optimal access node in a network region where the client terminal is located based on the content request, and the edge server obtains the data requested by the content request by accessing the optimal access node, thereby achieving a purpose of domain name-based data scheduling.

Therefore, the scheme of the above embodiment 6 provided by the present application solves the technical problem of low hit rate caused by the fact that the playing request is scattered to multiple CDN nodes in the process of playing the video in the prior art.

Optionally, the edge server is further configured to determine whether the content request is a request after stream granularity scheduling, and if so, respond to the content request and return a response result to the client terminal; if not, a scheduling policy at the flow granularity is requested from the edge scheduler.

Optionally, the edge scheduler is further configured to receive the content request, query whether data requested by the content request is cached locally, and return the data to the client terminal through the edge server if the data requested by the content request is cached locally.

Optionally, the edge scheduler is further configured to, if the data requested by the content request is not cached locally, obtain the data requested by the content request by accessing a scheduling center of the content distribution network, and return the data to the client terminal.

Optionally, the scheduling center is further configured to receive a content request sent by the edge scheduler, determine a network region where the client terminal is located according to address information of the client terminal, determine an optimal access node in the network region according to a domain name and a data stream, and return address information of the optimal access node to the edge scheduler, so that the edge scheduler obtains data requested by the content request by accessing the optimal access node.

Optionally, the edge scheduler is further configured to send the address information of the optimal access node to the edge server after receiving the address information of the optimal access node returned by the scheduling center, and locally cache an analysis result, where the analysis result is that the edge server obtains data requested by the content request by accessing the optimal access node.

Optionally, the edge server is further configured to send the data to the client terminal after obtaining the data requested by the content request by accessing the optimal access node, and locally cache the data requested by the content request.

Optionally, the edge server is further configured to send address jump information to the client terminal after acquiring the data requested by the content request by accessing the optimal access node, wherein the address jump information causes a web page on the client terminal to jump to a web page of the requested data.

Example 7

According to an embodiment of the present application, an embodiment of a data scheduling system based on a domain name system is provided, including:

a processor; and

a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: completing domain name scheduling in a content distribution network to obtain address information of an edge server in the content distribution network; sending a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

In the solution provided by the foregoing embodiment 7 of the present application, a client terminal completes domain name scheduling in a content distribution network, may obtain address information of an edge server in the content distribution network, sends a content request to the edge server based on the address information, and receives data returned by the edge server in response to the content request, where the data may be data locally cached by the edge server or data requested by the edge server from a scheduling center, so as to achieve a purpose of domain name-based data scheduling.

Therefore, the scheme of the embodiment 7 provided by the application solves the technical problem of low hit rate caused by that the playing requests are scattered to a plurality of CDN nodes in the process of playing the video in the prior art.

Example 8

The embodiment of the application can provide a computer terminal, and the computer terminal can be any one computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced with a terminal device such as a mobile terminal.

Optionally, in this embodiment, the computer terminal may be located in at least one network device of a plurality of network devices of a computer network.

In this embodiment, the computer terminal may execute the program code of the following steps in the data scheduling method based on the domain name system: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; (ii) a If the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

Alternatively, fig. 13 is a block diagram of a computer terminal according to an embodiment of the present application. As shown in fig. 13, the computer terminal a may include: one or more processors 1302 (only one of which is shown) and memory 1304.

The memory may be configured to store software programs and modules, such as program instructions/modules corresponding to the data scheduling method and apparatus based on the domain name system in the embodiment of the present application, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, implements the data scheduling method based on the domain name system. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory may further include memory remotely located from the processor, and these remote memories may be connected to terminal a through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The processor can call the information and application program stored in the memory through the transmission device to execute the following steps: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

Optionally, the processor may further execute the program code of the following steps: the method comprises the steps that a scheduling center receives a content request sent by an edge server; the dispatching center determines the network area where the client terminal is located according to the address information of the client terminal; the scheduling center determines an optimal access node in the network area according to the domain name and the data stream; and the dispatching center returns the address information of the optimal access node to the edge server, so that the edge server acquires the data requested by the content request by accessing the optimal access node.

Optionally, the processor may further execute the program code of the following steps: the edge server returns the data requested from the optimal access node to the client terminal and caches the data requested by the content request locally.

Optionally, the processor may further execute the program code of the following steps: after the client terminal sends the content request to the edge server based on the address information, the edge server judges whether the content request is a request after stream granularity scheduling; if yes, the edge server responds to the content request and returns a response result to the client terminal; if not, the edge server requests a scheduling policy at the flow granularity from the edge scheduler.

Optionally, the processor may further execute the program code of the following steps: after the edge server requests a scheduling policy of a stream granularity from the edge scheduler, the edge scheduler receives a content request; the edge scheduler inquires whether the data requested by the content request is cached locally; if the edge scheduler has cached the data requested by the content request locally, the edge scheduler returns the data to the client terminal through the edge server.

Optionally, the processor may further execute the program code of the following steps: if the edge scheduler does not locally cache the data requested by the content request, the edge scheduler acquires the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

Optionally, the processor may further execute the program code of the following steps: the scheduling center receives a content request sent by the edge scheduler; the dispatching center determines the network area where the client terminal is located according to the address information of the client terminal; the scheduling center determines an optimal access node in the network area according to the domain name and the data stream; the dispatching center returns the address information of the optimal access node to the edge dispatcher, so that the edge dispatcher acquires the data requested by the content request by accessing the optimal access node.

Optionally, the processor may further execute the program code of the following steps: and after receiving the address information of the optimal access node returned by the scheduling center, the edge scheduler sends the address information of the optimal access node to the edge server and caches an analysis result locally, wherein the analysis result is data requested by the edge server for acquiring the content request by accessing the optimal access node.

Optionally, the processor may further execute the program code of the following steps: after the edge server obtains the data requested by the content request by accessing the optimal access node, the edge server sends the data to the client terminal and locally caches the data requested by the content request.

Optionally, the processor may further execute the program code of the following steps: after the edge server obtains the data requested by the content request by accessing the optimal access node, the edge server sends address jump information to the client terminal, wherein the address jump information enables the webpage on the client terminal to jump to the webpage of the requested data.

By adopting the embodiment of the application, the client terminal finishes domain name scheduling in the content distribution network, can obtain the address information of the edge server in the content distribution network, sends the content request to the edge server based on the address information, and receives the data returned by the edge server responding to the content request, wherein the data can be the data locally cached by the edge server or the data requested by the edge server from the scheduling center, thereby realizing the purpose of domain name-based data scheduling.

The processor can call the information and application program stored in the memory through the transmission device to execute the following steps: the method comprises the steps that an edge server receives a content request sent by a client terminal, wherein the client terminal finishes domain name scheduling in a content distribution network to obtain address information of the edge server in the content distribution network; if the edge server caches the data requested by the content request locally, the edge server sends the data corresponding to the content request to the client terminal, wherein the content request at least comprises the following steps: domain name, address information of client terminal; if the edge server does not cache the data requested by the content request locally, the edge server acquires the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

Optionally, the processor may further execute the program code of the following steps: after the edge server receives a content request sent by a client terminal, the edge server judges whether the content request is a request after stream granularity scheduling; if yes, the edge server responds to the content request and returns a response result to the client terminal; if not, the edge server requests a scheduling policy at the flow granularity from the edge scheduler.

It can be understood by those skilled in the art that the structure shown in fig. 13 is only an illustration, and the computer terminal may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palmtop computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 13 is a diagram illustrating a structure of the electronic device. For example, the computer terminal a may also include more or fewer components (e.g., network interfaces, display devices, etc.) than shown in fig. 13, or have a different configuration than shown in fig. 13.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

Example 9

Embodiments of the present application also provide a storage medium. Optionally, in this embodiment, the storage medium may be configured to store a program code executed by the domain name system-based data scheduling method provided in the first embodiment.

Optionally, in this embodiment, the storage medium may be located in any one of computer terminals in a computer terminal group in a computer network, or in any one of mobile terminals in a mobile terminal group.

Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: the client terminal finishes domain name scheduling in the content distribution network to obtain the address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; if the edge server does not locally cache the data requested by the content request, the client terminal will receive the data requested by the edge server through the scheduling center accessing the content distribution network.

Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: the method comprises the steps that an edge server receives a content request sent by a client terminal, wherein the client terminal finishes domain name scheduling in a content distribution network to obtain address information of the edge server in the content distribution network; if the edge server caches the data requested by the content request locally, the edge server sends the data corresponding to the content request to the client terminal, wherein the content request at least comprises the following steps: domain name, address information of client terminal; if the edge server does not cache the data requested by the content request locally, the edge server acquires the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. A data scheduling method based on a domain name system comprises the following steps:

the client terminal finishes domain name scheduling in a content distribution network to obtain address information of an edge server in the content distribution network;

the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of the client terminal;

if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server;

and if the edge server does not locally cache the data requested by the content request, the client terminal receives the data requested by the edge server through a dispatching center accessing the content distribution network.

2. The method of claim 1, wherein the edge server requesting the data by accessing a dispatch center of the content distribution network comprises:

the dispatching center receives the content request sent by the edge server;

the dispatching center determines the network area where the client terminal is located according to the address information of the client terminal;

the scheduling center determines an optimal access node in the network region according to the domain name and the data stream;

and the dispatching center returns the address information of the optimal access node to the edge server, so that the edge server acquires the data requested by the content request by accessing the optimal access node.

3. The method of claim 2, wherein the edge server returns the requested data from the optimal access node to the client terminal and caches the requested data for the content request locally.

4. The method of claim 1, wherein after the client terminal sends a content request to the edge server based on the address information, the method further comprises:

the edge server judges whether the content request is a request after stream granularity scheduling;

if yes, the edge server responds to the content request and returns a response result to the client terminal;

if not, the edge server requests a scheduling policy at the flow granularity from the edge scheduler.

5. The method of claim 4, wherein after the edge server requests a flow-granular scheduling policy from an edge scheduler, the method further comprises:

the edge scheduler receiving the content request;

the edge scheduler inquires whether the data requested by the content request is cached locally;

and if the edge scheduler locally caches the data requested by the content request, the edge scheduler returns the data to the client terminal through the edge server.

6. The method of claim 5, wherein if the edge scheduler does not locally cache the data requested by the content request, the edge scheduler obtains the data requested by the content request by accessing a scheduling center of the content distribution network and returns the data to the client terminal.

7. The method of claim 6, wherein the edge scheduler obtaining the data requested by the content request by accessing a scheduling center of the content distribution network comprises:

the scheduling center receives the content request sent by the edge scheduler;

and the dispatching center returns the address information of the optimal access node to the edge dispatcher, so that the edge dispatcher acquires the data requested by the content request by accessing the optimal access node.

8. The method of claim 7, wherein after receiving the address information of the optimal access node returned by the scheduling center, the edge scheduler sends the address information of the optimal access node to the edge server and locally caches a resolution result, wherein the resolution result is that the edge server obtains the data requested by the content request by accessing the optimal access node.

9. The method of claim 7, wherein after the edge server obtains the data requested by the content request by accessing the optimal access node, the method further comprises:

and the edge server sends the data to the client terminal and locally caches the data requested by the content request.

10. The method of claim 7, wherein after the edge server obtains the data requested by the content request by accessing the optimal access node, the method further comprises:

and the edge server sends address jump information to the client terminal, wherein the address jump information enables the webpage on the client terminal to jump to the webpage of the requested data.

11. A data scheduling method based on a domain name system comprises the following steps:

an edge server receives a content request sent by a client terminal, wherein the client terminal finishes domain name scheduling in a content distribution network to obtain address information of the edge server in the content distribution network;

if the edge server caches the data requested by the content request locally, the edge server sends the data corresponding to the content request to the client terminal, wherein the content request at least comprises the following steps: domain name, address information of the client terminal;

and if the edge server does not locally cache the data requested by the content request, the edge server acquires the data requested by the content request by accessing a dispatching center of the content distribution network and returns the data to the client terminal.

12. The method of claim 11, after the edge server receives the content request sent by the client terminal, the method further comprising:

13. A domain name system based data scheduling system comprising:

a client terminal, configured to complete domain name scheduling in a content distribution network, obtain address information of an edge server in the content distribution network, and send a content request based on the address information, where the content request at least includes: domain name, address information of the client terminal;

the edge server is used for receiving and responding to the content request and returning the data obtained by the request to the client terminal;

the dispatching center is used for receiving the content request sent by the edge server if the edge server does not locally cache the data requested by the content request, and determining the optimal access node in the network area where the client terminal is located based on the content request;

and the edge server acquires the data requested by the content request by accessing the optimal access node.

14. A domain name system based data scheduling system comprising:

the edge server is used for receiving the content request and judging whether the content request is flow granularity scheduling or not;

an edge scheduler, configured to receive the content request after the edge server determines that the content request is not the stream granularity scheduling;

the scheduling center is used for receiving the content request sent by the edge scheduler and determining the optimal access node in the network area where the client terminal is located based on the content request if the edge scheduler does not locally cache the data requested by the content request;

15. A storage medium comprising a stored program, wherein the program, when executed, controls an apparatus in which the storage medium is located to perform the steps of: the client terminal finishes domain name scheduling in a content distribution network to obtain address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of the client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; and if the edge server does not locally cache the data requested by the content request, the client terminal receives the data requested by the edge server through a dispatching center accessing the content distribution network.

16. A mobile device, comprising: a processor for executing a program, wherein the following steps are performed when the program is executed: the client terminal finishes domain name scheduling in a content distribution network to obtain address information of an edge server in the content distribution network; the client terminal sends a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of the client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; and if the edge server does not locally cache the data requested by the content request, the client terminal receives the data requested by the edge server through a dispatching center accessing the content distribution network.

17. A domain name system based data scheduling system comprising:

a processor; and

a memory coupled to the processor for providing instructions to the processor for processing the following processing steps: completing domain name scheduling in a content distribution network to obtain address information of an edge server in the content distribution network; sending a content request to the edge server based on the address information, wherein the content request at least comprises: domain name, address information of client terminal; if the edge server caches the data requested by the content request locally, the client terminal receives the data directly returned by the edge server; and if the edge server does not locally cache the data requested by the content request, the client terminal receives the data requested by the edge server through a dispatching center accessing the content distribution network.